Please enable JavaScript.
Coggle requires JavaScript to display documents.
ASOS QA Engineer (Core Attributes (Customer Focussed, Passionate,…
ASOS QA Engineer
-
Testing
-
Execution
Exploratory
Plans their testing activities using some form of Exploratory Testnig method such as RST/Test Sessions/Test Charters/Session based testing
-
Demonstrates an ability to use Exploratory Testing outside of UI focused journeys focusing on APIs or other technologies where appropriate
-
-
Demonstrates an ability to focus their testing on specific risks and chooses the appropriate approach for best results
Strategy
Understands why parts of the Test Strategy are not implemented in the team and their associated risks
-
Demonstrates an understanding of how their platform perform testing at different stages of the lifecycle (Test -> PreProd -> Prod)
-
Pairing
Pairs with other Testers on the team, contributing to their testing session
-
-
-
Static Analysis
Actively contributes to 3 Amigos & refining and drives the conversation into a Test Plan for the story
-
-
-
Coverage
-
-
-
Has the ability to identify the right software testing types that cover the risks associated with the application
-
Collaboration
Collaborates with other teams in the platform and the wider tech organisation to achieve their testing goals
-
-
-
-
-
-
Technical
Architecture
Understands how the application hangs together. Can confidently explain and talk people through how it all works, the technologies used.
-
-
Tooling
Demonstrated good tooling choice decisions and expertise, describing the tooling necessary to facilitate the level of testing required.
Investigates usefulness of new tools that may aid testing efforts and communicates their findings to their team and the wider QA group.
-
-
Testability
Can use mocks, stubs and other approaches to provide necessary test data and states to aid their testing efforts.
Can work with developers to modify application code and mocks/stubs to ensure a more testable application.
-
Pipeline
-
-
Understands the 'checking' needs of the pipeline and can evaluate their testing effectiveness at all levels and stages of the pipeline
-
Goals
-
Build a Software Tester who can influence the architectural, design and implementation of the application to improve testability
-
-
Code & Automated Checks
Coverage
Has demonstrated an ability to author tests of all types at differing levels, in line with the needs of the team.
-
Monitors the performance of their Automated Checks and continually improves them for reliability, coverage and speed.
Engineering
-
-
Identifies when automation can be used to aid testing & works with others to create tools to aid with testing efforts
-