Description
The test strategy pyramid:
* = Manual | user acceptance testing
** = Manual | exploratory testing
*** = End-to-End | Smoke screen automation (browser-based testing in production)
**** = End-to-End | CI; Browser-based
***** = End-to-End | CI; Headless & API
****** = Integration | CI; Contract tests (consumer/provider of services)
******* = Integration | CI; External-service
******** = Integration | CI; Controller-level aka DB-integration
********* = Unit | CI; UI tests
********** = Unit | CI; Backend/functionality tests
The goal of testing is not 100% code coverage, but the appropriate amount of effort to ensure the least amount of value disruption for our clients and greater viability from the perspective of our client-facing teams (fewer "value-impeding" bugs = better experience for everyone).
This ability is influenced by this article on the testing pyramid.
Milestone 1
I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to a squad when wielding this ability, and therefore I would put them in situations where they can employ this ability with only a small amount of guidance
Milestone 2
I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to a squad when wielding this ability, and therefore I would put them in situations where they can employ this ability, with no assistance as well as being a trusted active or passive mentor to others
Milestone 3
I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to multiple squads when wielding this ability, and therefore I would put them in situations where they can employ this ability as well as being considered an expert within this discipline
Milestone 4
I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to a squad when wielding this ability, and therefore I would put them in situations where they can not only employ this ability but where they set the tone for this at the company level
Milestone 5
I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to not just internal teams but the community/industry in general when wielding this ability, and they are recognized by the community/industry as an expert
Configuration Health
- 🛑 Associated with no roles
 - ⚠️ Has been referenced in no observations
 - ℹ️ No one has achieved a milestone on this ability
 
- ⛔️ Last updated: over 3 years ago
 - ℹ️ Never conversed about
 
Role & Position Requirements
- --No roles require this ability--
 
Examples / Observations
An observation relating to unused test automation has not been publicly recognized yet.
Conversations about unused test automation
This section is for Lessonly folks only. Sign your team up to find your Gruuv!