Delivery
Testing and QA
Quality is not a phase parked after the date has already slipped. ISTQB-certified testers treat testing as prevention and evidence: automated checks in the pipeline, exploratory checks where judgement matters, and acceptance by the client.
In brief, then in detail
- Prevention before detection. Clear acceptance criteria, code review, and tests written with the change. A bug that never enters the main line is cheaper than a bug found in production.
- The right layer of test. Unit tests for logic, integration tests for contracts, and a smaller set of end-to-end tests for the journeys that carry the business.
- Performance and security. Load where the risk is real. Dependency and configuration review. Secrets do not live in the repository. Findings are triaged, not buried.
- Acceptance. The people who will use the product, or a delegate who truly represents them, exercise the increment. Their sign-off is evidence, not a ceremony.
How it is run
Quality management here means the standard is agreed, the work is checked against it, and gaps are recorded. A sprint item is not done because a developer says it works on their machine. The pipeline, the review, and the acceptance criteria have to agree. Defects found late are treated as information about the process, and the retrospective is expected to change something.
In the sprintTests belong with the change
EvidenceA pipeline, not a speech
AcceptanceClient users, on the real journeys
Quality toolkit
- Jest
- Cypress
- Playwright
- Selenium
- JMeter
- Postman
- SonarQube
Terms, in plain language
- Acceptance criteria. The conditions that make a backlog item done, written before the sprint pretends to finish it.
- Regression. Proof that today’s change did not break yesterday’s promise. Automated where the journey is stable.
- User acceptance. The client’s own check that the software does the job in their context. It is not a substitute for engineering tests.
- Severity. How bad a defect is for the business. Priority is when it will be fixed. They are not the same word.