Blog & articles

Latest post

Splitting Test Strategy Decisions Between Your Team and Embedded QA Engineers
Splitting Test Strategy Decisions Between Your Team and Embedded QA Engineers
The most reliable way to split test strategy decisions is by the kind of knowledge each decision needs. Your internal team should own the decisions that depend on product and business context. That means risk tolerance, release criteria, and which user outcomes can never break. Embedded QA engineers should own the decisions that depend on testing craft: coverage design, test structure, regression tiering, and failure triage. The guidance below reflects how that division holds up inside working engineering teams.
What Happens to Your Automated Test Suite When Your Only SDET Leaves
What Happens to Your Automated Test Suite When Your Only SDET Leaves
When your only SDET leaves, your automated test suite does not fail on day one. It decays. The tests keep running, but nobody remembers why specific checks exist. Flaky failures get muted instead of fixed. New features ship without coverage. Eventually the suite no longer reflects where your product can break. The fix is to move suite knowledge out of one person's head and into three places: readable code, documented coverage decisions, and a named maintenance owner.
Who Maintains Tests Written by Augmented QA Contractors After the Contract Ends?
Who Maintains Tests Written by Augmented QA Contractors After the Contract Ends?
When a QA contract ends, the tests stay and the context leaves with the contractor. Unless someone plans for it, maintenance falls to whoever is closest to the failing pipeline. That is usually a developer who never wrote those tests and has no time to learn them. The real answer is that an owner must be named before the contract ends. That owner is either an internal QA engineer or SDET supported by a proper handoff, or a managed QA service that owns upkeep while you own the code.
Should Managed Playwright Tests Block Pull Requests or Only Report Failures?
Should Managed Playwright Tests Block Pull Requests or Only Report Failures?
Blocking every pull request on a managed Playwright suite is the fastest way to teach developers to ignore it. The better answer is a split. A small tier of fast, stable tests that cover your highest-risk workflows should block merges. The broader regression suite should report its failures to someone who triages them quickly. When managed Playwright suites run inside client CI pipelines, a human QA expert reviews every failure before developers are notified.

Subscribe to our newsletter