Choose a route. Build useful QA evidence.

You can identify a product risk and locate its place in the delivery workflow.

• Derive test conditions from risks and requirements.
• Select a suitable test design technique.
• Report a reproducible defect without guessing its cause.

Create a test charter, a small set of designed tests, and one example defect report.

Each test connects to a risk, and the defect report contains reproducible evidence and a clear effect.

You can design a useful repeatable test and explain why automation is appropriate.

• Choose one language for a stated team need.
• Write a small deterministic automated check.
• Explain the maintenance and diagnostic needs of the check.

Build one automated check with controlled data, a meaningful assertion, and a useful failure message.

A second person can run the check, understand its purpose, and diagnose an intentional failure.

You have stage evidence that shows manual, technical, or automated QA work.

• Summarize coverage, evidence, uncertainty, and release options.
• Use production signals to improve future testing.
• Present QA work as a reviewable professional artifact.

Prepare a release recommendation and a compact portfolio case study from your roadmap evidence.

Both artifacts link claims to evidence, state important limits, name the decision owner, and identify the next learning need.