Designs for Vision of Testing Categories
Let's create some mocks for some future Testing Features (test history, code quality dashboard, etc.) that will live in the Premium and Ultimate tier. This well give us artifacts to point at when we talk to prospects about the roadmap and value coming soon and get feedback on those items.
Todos
-
Identify the 3 - 5 problems to solve that would require mocks - Where are the "hot spots" in our code?
- What projects have low code coverage / low code quality?
- What projects poor low accessibility, web performance and load performance?
- What tests are flaky?
- test insights
- What projects "cost the most"
- What projects have the slowest pipelines?
- What projects are the highest minutes / green pipeline?
- What projects have tests pass in testing and fail in production?
- cross stage with progressive delivery
- Where are the "hot spots" in our code?
-
Discuss workflow / outcomes for using each - Hot Spots for code - As a Director I can see a dashboard of low code coverage / quality projects, so that I can direct the team to focus on projects that may have bugs in them.
- Hot Spots for performance - As a Director I can see a dashboard of low performing projects, so that I can direct the team to focus on projects where we can quickly improve the user experience.
- Costly Tests - As a director, I want to see a view of my most costly (take a lot of time to run and fail a lot) tests, so that I can direct the team to fix that and save us money.
- Post Deploy Bugs - As a director, I want to see which projects rollback most often, so I can focus my teams on fixing those bugs / code and stop costly fixes.
-
Create the mocks -
Distribute internally for discussion -
Add to appropriate direction page(s) -
Review with PMM for inclusion in Use Case page
Edited by James Heimbuck