Begins to apply exploratory testing techniques following guidance and training materials
Starts to write and communicate simple bug reports with guidance
Attends and starts to add value squad rituals
Uses tool assisted testing techniques to identify symptoms of bugs
Proactive in asking questions, explains what they have tried so far and why that hasn’t worked
Analyses features, understands impact of change can analyse what areas will be affected by a change
Independently creates test scenarios for business features with high customer visibility and medium business risk
Writes detailed bug reports according to best practice. Communicates clearly to the engineers with little need for clarification
Independently uses tool assisted testing techniques to assist in determining a bug’s root cause
Drives releases from a test perspective. Understands the need for quality and weighs up bug impact vs feature impact to assist release decisions
Participates in squad rituals
Employs appropriate exploratory testing techniques
Proactive in asking questions to identify areas of risk
Self learns new techniques and tools and seeks out people who can assist them
Leads conversations when analysing features, advocates for acceptance criteria to be included (Example: advocates for accessibility acceptance criteria to be included in a front-end story)
Creates test scenarios for business features with high customer visibility and high business risk. Advises others on how to create test scenarios
Advises on testing approach for a feature, advocates for testing lower down the test pyramid (Example: pushes testing of some acceptance criteria down into the unit tests, works with developers to help that happen)
Writes detailed bug reports, communicates to developers, advocates for fixes, contributes to defining best practice
Debugs complex defects, able to capture root cause (not just symptoms)
Identifies areas of testing within the business that can be improved and suggests improvements