Quality is everyone’s responsibility yet, It’s very common and acceptable saying in the teams that, ignore this failure, it’s due to flaky test. What if I say, there is no such thing as flaky test, your app is flaky! Quite often flakiness implies its test problem and no one needs to worry about it but what if our test found the bug before we released in production and we just ignored it? Flaky test are not useless, they are telling you something. As a team, we need to look into flakiness insights to work on making app more reliable and testable. Automation is not end goal and 100% automation is myth. We need to work on quality instead of quantity. One flaky test in the build can make team not to trust on the tests even if they might be reliable. Test should be treated with same care as application code. Is team focused only on delivering new and shiny features but not thinking about resiliency and testability? The highest degree of testability in your app will lead to lowest flakiness. We really need to change our perspective and start thinking why this test is flaky and what we can do as a team to make these test reliable?

Key Learnings –

• What test should we automate?
• Listen to your flaky test results, its opportunity to improve your product!
• Why automation should be owned by entire team?
• How can we reduce flakiness?