Code Testing and Coverage Category Maturity Research
What’s this issue all about?
We want to measure the maturity of the Code Testing and Coverage category for a scheduled move in Q3.
What hypotheses and/or assumptions do you have?
We assume has met the main JTBD and that since many internal users make use of the Test Summary Widget and JUnit Report that this category can move to Viable.
What questions are you trying to answer?
Can users complete their main JTBD:
- When I build my project, I want to review test result data, so that I can identify failures and improve code quality.
- When I want to see a high level quality measure, I want to know how much code in my project is covered by tests, so that I can target improvements for areas of the project that do not have tests.
Core questions
TBD
Additional questions
TBD
What persona, persona segment, or customer type experiences the problem most acutely?
Developers.
What business decisions will be made based on this information?
The maturity of Code Testing and Coverage will advance OR stay put and we will know more validation research is needed.
Links / References
Edited by James Heimbuck