-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Epic: Comprehensive Test Plan Implementation #18396
Comments
gracekretschmer-metrostar
added
Epic
Issue type
Needs refining
Issue status
CMS Team
CMS Product team that manages both editor exp and devops
labels
Jun 25, 2024
This was referenced Jun 25, 2024
30 tasks
30 tasks
24 tasks
34 tasks
29 tasks
35 tasks
42 tasks
32 tasks
gracekretschmer-metrostar
changed the title
Implementation: Comprehensive Test Plan
Epic: Comprehensive Test Plan Implementation
Oct 28, 2024
36 tasks
34 tasks
33 tasks
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Status
Update each sprint until completed
Background
For CMS development, test plans and test scripts have historically been created by developers without QA engineering oversight and right now, flakey tests and testing gaps have created errors during the daily deploy process. @keisterj-oddball did discovery work to determine how to approach a comprehensive test plan and now the comprehensive test plan needs to be implemented.
User Story or Problem Statement
As an editor in Drupal CMS, I need to know that when there are updates to Drupal CMS, it will not unintentionally impact other areas of Drupal CMS that are critical for my day-to-day work.
As a developer in Drupal CMS, I need to know if and how my code changes in Drupal CMS unintentionally impact other areas of Drupal CMS.
As a developer in Drupal CMS, I need to have confidence that the test scripts in Drupal CMS are providing accurate and quick results that I can use to shape my code.
Affected users and stakeholders
Hypothesis
By implementing a comprehensive test plan for CMS, we will be able to better catch bugs and bad code before it goes into production and impacts editors and veterans.
Desired Outcomes
OCTO OKR
Objective: Our platforms are the best way to deliver products at VA
Key Results: Our platforms hit the “elite” level (as defined by DORA) on Deployment Frequency, Lead Time for Changes, Change Failure Rate, and Time to Restore Service
Reference Links
Definition of Done
Tasks
The text was updated successfully, but these errors were encountered: