This is why the prevalence of flaky tests and what you vày when they occur matters so much. Flakiness left unguarded, will destroy the trust people have sầu in their tests.
Bạn đang xem: Flaky là gì
If there is rampant, inadequately addressed flakiness in your tests, then you can’t trust the tests.If you can’t trust the tests, then you can’t trust the code.If you can’t trust the code, then you can’t trust developers.If you can’t trust developers, then you can’t trust your team.If you can’t trust your team, then you can’t trust the organization.If you can’t trust your organization, then there’s obviously a laông xã of trust in the culture, which means you work at a company with an unhealthy culture.If your company has an unhealthy culture, your job satisfaction will steadily decline.
There will be a tipping point where you transition from thinking about your organization as an organization that has flaky tests, khổng lồ the kind of organization that has flaky tests. Once you make the mental shift & believe sầu it’s because of the organization that there are so many flaky tests, trust in the organization has been eroded.
With job satisfaction continuing to lớn plummet, it’s at this time that your top engineering talent will begin looking elsewhere, actively searching, or maybe just a little more willing to lớn open the emails & messages from recruiters that they had been previously ignoring.
The saving grace of this situation is that this degradation happens over time. With the right strategies và tools, you can mitigate and even reverse the damage. But it’s not easy, and you can’t vì chưng it alone.
Flaky tests aren’t going away
Flakiness is only getting worse, not better. As your codebase & test suites grow, so too will the number of flaky tests & results. As you transition, or if you’re already using a microservice architecture, you can have many dependencies. As dependencies increase, flakiness is magnified.
For example, even if all of your microservices have 99.9% stability, if you have 20+ dependencies each with the same stability, you actually end up having a non-trivial amount of flakiness:
98.01% stability for đôi mươi dependencies97.04% stability for 30 dependencies95.12% stability for 50 dependencies
As your engineering organization scales, how it addresses flakiness will be one of the most important factors impacting overall productivity.
A presentation was released by Google, The State of Continuous Integration Testing