Testing First: Adopting a Test‑First Mindset for Effective Software Development
The article explains that viewing testing as a mindset is essential for developers, outlines how to decide what to test—through user journeys, new features, and bugs—compares manual and automated testing, discusses the shift of testing responsibilities leftward, and clarifies who should own testing within various team structures.
Recognizing that testing is a mindset is crucial for writing automated tests; without this awareness, tools and frameworks become irrelevant.
Development and QA teams view applications differently—developers build software while QA aims to break it—so developers must learn to think like testers to translate that mindset into automation.
When new features or bugs arise, the first step is to consider how to test the related code, involving both developers and testers in the discussion.
Even if a QA team only performs manual testing, their input is valuable for defining test cases that developers can convert into automated tests; if no dedicated QA exists, the development team should decide what tests are needed.
A practical approach starts from the end goal: identify what the new feature should accomplish, break it into incremental steps, and turn those steps into tests, often captured as acceptance criteria in user stories for agile teams.
To determine what to test, focus on three areas:
User Journey – Identify the most critical parts of the application (e.g., login, purchase, payment) and write end‑to‑end tests that cover the entire user flow rather than isolated steps.
New Feature – For each new capability, ask what it should do and what problem it solves, then decompose it into small steps that become automated test cases.
Bug – Write an automated test that reproduces the bug before fixing it; after the fix, the test should pass, ensuring the bug does not reappear.
Manual testing involves a person (often QA) interacting with the application, which is time‑consuming and unsuitable for frequent deployments.
Automated testing, combined with CI/CD pipelines, enables teams to push code to production multiple times a day, embodying the “test‑left” movement where developers take on more testing responsibilities early in the development lifecycle.
Testing is ultimately everyone's responsibility, and modern software companies adopt one of three structures: dedicated development and QA teams, cross‑functional squads (designer, developer, QA), or full‑stack solo developers, each requiring shared ownership of quality.
Continuous Delivery 2.0
Tech and case studies on organizational management, team management, and engineering efficiency
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.