Strategy and processes

How testing is organized beyond the individual test: the agile strategy, deciding what gets tested at which layer, and the quality processes around development.

Strategy

• Agile testing strategy — testing inside the cycle, RACI, and the lifecycle of a test (progression → regression).
• Defining tests for a feature — from acceptance criteria to test cases, and from test cases to layers.
• Backend testing layers — unit / integration / API E2E, with examples.
• Frontend testing layers — unit / component / E2E, and who writes what.
• What E2E tests should cover — the 8–12 rule, which stories deserve an E2E, and cross-domain flows.
• Microservices testing — isolated vs integrated, contract testing and tooling.
• Test environments strategy — what each environment can prove, where to pay each risk, and shared-environment hygiene.
• Mocks in integration testing — designing mocks that don't lie, and recognizing the ones that do.

Quality processes

• Shift-left and the maturity model — 6 dimensions × 5 levels to assess your team.
• Acceptance criteria and Definition of Ready — the artifacts that prevent bugs before any code exists.
• Bug root cause analysis — the taxonomy and what to do with the data.
• How to review a task — reviewing feature tickets and peer review between QAs.
• Scrum from the QA seat — what QA does in each ceremony, estimation that includes testing, and team metrics.
• Test management in Jira with Xray — tests, plans and executions, honest verdicts and the workflow that keeps traceability.
• Investigating hard failures — intermittent bugs and production incidents: control runs, fair comparisons and evidence.