organize automated tests without getting eaten by your devs
Blog post from Octomind
Octomind has developed a strategy to maintain a trustworthy and efficient testing pipeline while avoiding developer frustration caused by flaky tests. Instead of relying on the traditional testing pyramid, Octomind employs an hourglass-shaped approach, emphasizing a strong base of unit tests with quick execution, a minimal set of integration tests for critical cross-component behaviors, and a substantial, stable layer of end-to-end (e2e) tests. The company introduces a rotating role known as OctoQA, where team members take turns managing new e2e tests in a staging environment before they are integrated into the main pipeline. This process ensures that only stable tests are promoted, maintaining the pipeline's reliability and credibility. If any test becomes flaky after integration, it is immediately quarantined for further investigation and improvement. Through this system, Octomind fosters trust, shared responsibility, and a focus on maintaining software quality across the team.