Skip to content
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

Create a QA test plan and regression test plan for Operating Statuses #19808

Closed
3 of 4 tasks
jilladams opened this issue Nov 6, 2024 · 2 comments
Closed
3 of 4 tasks
Assignees
Labels
Facilities Facilities products (VAMC, Vet Center, etc) Manual QA Needs refining Issue status Regional office CMS managed VBA product owned by the Facilities team sitewide VAMC CMS managed product owned by Facilities team Vet Center CMS managed product owned by Facilities team

Comments

@jilladams
Copy link
Contributor

jilladams commented Nov 6, 2024

Description

We will modify Operating Statuses. We need to:

  1. Document how Operating Statuses work today in Production as a regression test plan, to ensure no regressions.
  2. Create a test plan for changes in this epic.

Testing & QA

Test plan is started: #13598 Facility Operating Status expansion test plan (A6 google sheets)

Scope / Impact analysis

What, if anything, could break as a result of this change?

Acceptance criteria

ACs should capture expected behavior, to inform test plans. Consider devices, documentation updates including KBs, change management, and content model when applicable.

  • Regression test plan for Operating Statuses has been created and reviewed for accuracy with engineers & Product, including:
    • Drupal behavior, within reason
    • FE behavior
  • Test plan for this iteration on Operating Statuses is created to cover behavior changes expected for the work
@laflannery
Copy link
Contributor

Drupal portion is completed I believe. Asked Christian and Michael if they would be able to review.

@laflannery
Copy link
Contributor

Front end feature testing and Regression testing have been added. I am closing this ticket because from my standpoint this is done but if other folks have any feedback/issues and feel this needs to be reopened, let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Facilities Facilities products (VAMC, Vet Center, etc) Manual QA Needs refining Issue status Regional office CMS managed VBA product owned by the Facilities team sitewide VAMC CMS managed product owned by Facilities team Vet Center CMS managed product owned by Facilities team
Projects
None yet
Development

No branches or pull requests

2 participants