1,561 karma · joined February 12, 2014
ajeet@tesults.com
Morality is constantly changing and what is considered treating someone poorly changes too. More recently it appears to be changing faster than ever. That can make it hard to remain with the bounds of what is in the current instance of time considered socially acceptable by the majority. There is no absolute morality even though it may seem like it if you are thinking with the span of an hour or a day. Stretch it out and it's a constant shifting. In any case, I don't think anyone should be silenced. If they say something that the majority feels is foolish, they can be considered a fool, or a debate can be had to convince them of why they may be wrong, but to silence externally, or increasingly, self silencing with self censorship, in my opinion is dangerous as that means ideas cannot be discussed openly.
This is the most popular method of doing things in my experience and the reason for that seems to be it makes chronological sense to a human brain. It’s very unnatural for people (including clever devs) to consider a project like manufacturing a car and starting with ‘the tire pressure should be correct’. Also too often (wrongly or rightly) prototypes often don’t have tests and that sets the tone quite early. Automated tests should be written ASAP no matter which methodology is used.
As for the test executioner/runner I have a custom Node.js application using Mocha test framework, and for reporting I use Tesults (https://www.tesults.com) which I recommend to everyone of course because because I think it's the best way to consolidate and report test results and I'm the founder :) Send me a message for anything reporting related and I'll do my best to help.
I’m founder at Tesults (https://www.tesults.com) where we have a flaky test indicator that makes identifying these tests easier. It’s free to try and if you can’t get budget for a proper plan send me an email and I’ll do what I can.
In general the only way to never have flaky tests is to have simpler tests but I find those often don’t provide as much value - that’s just my personal belief after having spent years focused on automated tests, e2e tests do have robustness issues but the bugs they find make them totally worth it. Out of the issues mentioned in the article that affected my tests the most, it’s timing. They can be overcome though, I’ve run test suites with a couple of thousand e2e tests (browser) that have been highly robust and reliable after time was devoted to hardening them. You do have to focus on that and refuse to add new test cases until the existing ones are sorted out in some cases.
The reason it doesn’t happen most of the time is because other than automating tests, where the benefit is super obvious, there’s no role or job assigned for automating stuff specifically. It’s usually done as part of another job, such as someone responsible for SRE. Automation doesn’t mean it’s set and forget, it needs maintenance, updating, as processes change. People often automate once, realise the process has changed, deem the automation a failure or useless now, and because things need to work right away (to take care of other deli erivables understandably) they don’t update the automation program but rather continue doing things manually because of the instant success of achieving it manually.
Automation takes upfront investment but the idea is it pays off over the long term. If people think processes are going to keep changing and the automation system is not flexible to deal with that it won’t happen. It needs a dedicated person to do this and maintain this in larger teams.
You also need to figure out a way to demonstrate the value of you having taken the time to automate something, especially if your management/leadership isn’t clear on it. Shameless plug, I work on Tesults (https://www.tesults.com) for reporting test results, and even though the primary aim of it is not to demonstrate the value of automation it is definitely a byproduct/side-effect, customers have said this.
Personally I’d focused on the obvious first: tests, build processes such as getting code from repos for building, release artifact output. For mobile apps for example have ipa and apk files automatically available for download by manual testers. Then go onto less obvious things like automated sprint creation for upcoming sprints in JIRA etc with their API. If in marketing, perhaps social media automation for things their apis allow.