Guest Post: Retrying your tests is actually a good thing (If your approach is right)

Filip Hric, a QA lead at Slido, discusses the pros and cons of implementing test retries in software testing, particularly in the context of Cypress version 5.0.0, which introduced native support for this feature. He emphasizes that while retries can be beneficial if used correctly, they should not be relied upon to mask or ignore underlying issues with flaky tests, which remain an anti-pattern in test development. The post highlights the importance of diagnosing the root causes of test failures, such as server issues or improperly written tests, and not merely using retries as a shortcut to pass tests. Hric shares his personal experience of achieving stability in tests by addressing speed-related failures and advises leveraging test analytics to strengthen tests prone to retries. He encourages testers to view retries as a tool for improving test robustness and understanding of the code, rather than a remedy for inadequate code, promoting a pragmatic approach to software testing that fosters continuous improvement and confidence in releases.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.