Please enable JavaScript.
Coggle requires JavaScript to display documents.
Associate QA Engineer (Testing (Execution (Exploratory (Can describe the…
Associate QA Engineer
Testing
-
Execution
Exploratory
Can describe the path taken through an exploratory testing session, highlighting areas that weren't covered and explains why certain paths were covered against others.
-
-
-
-
-
Pairing
Regularly pairs with others on the team, contributing to the session
-
-
Coverage
-
Can describe the Test Coverage for a Story worked on using Safe Language to indicate that not everything can or should be tested
-
Domain Knowledge
Can explain how the platform fits into the overall ASOS journey. The importance it plays in creating a first class customer experience
-
Technical
-
Tools
Can comfortably demonstrate their use of testing tools (think Postman, Fiddler, Chrome Dev Tools - whatever is appropriate) or equivalent
-
-
-
-
-
-
Transition To Mid
-
-
-
Testing
-
-
Strategy
Understands why parts of the Test Strategy are not implemented in the team and their associated risks
-
-
-
Code & Automated Checks
-
Coverage
Can describe the different types of automated checks used to test the application and the value they bring
-
-
Goals
Become a Software Tester that recognises their role and is able to provide information about the product and use 'Safety Language' when discussing test coverage and software quality.
Build a Software Tester who asks well informed questions that highlight risks and challenges, helping the team create better quality experiences through informed decision making, despite pressures to just get things done
-
Build a Software Tester that demonstrates a collaborative nature that involves sharing and working within their team and others across the platform
-