Front End: QA test artifact for VBA Regional Office Pilot MVP collab cycle staging review

[xiongjaneg]

Description or Additional Context

For VBA Regional Office Pilot MVP collab cycle staging review, we'll need QA artifacts. This ticket is to create a QA artifact document that captures the required elements.

A Tugboat environment is acceptable with 2 additional days for collab cycle review. This should be a new Tugboat just for this review.

Required elements

An artifact that corresponds to each standard in the QA Standards.

• Regression test plan
• Test plan
• Coverage for References
• Summary(Defects) reports
• E2E tests (provide a link to the product’s code provide a screenshot)

  • Platform states Eli's plan is acceptable given our constraints:
    E2E testing really should be done on static data, not on dynamic editor-built data. We can build fake data in a mock and test it with the renderHTML feature of content-build which "renders" the page. This is not the same as rendering the page with cypress and therefore is not a complete E2E test but it is more than component testing and can test edge cases. However, the feature set of the rendered pages in terms of being able to access certain shadow-root components supplied by the DST is limited when testing this way.

  • The pages are not static. They are dynamic. But dynamic drupal content-build not dynamic vets-website. So E2E cypress is a challenge to test or nearly impossible if the drupal content changes which it may do very rapidly.

  • renderHTML doesn't produce any visual output so it doesn't generate artifacts. It's usually outputted just like the unit tests. We could screenshot and highlight the lines of the unit-test output that cover the rendered pages.

• Code coverage (provide a link to the product’s code)

Example

PACT Act example

Acceptance Criteria

• Link to QA artifact [insert here]
  • Contains Regression test plan
  • Contains Test plan
  • Contains Coverage for References
  • Contains Summary(Defects) reports
  • Contains E2E tests (provide a screenshot and highlight the lines of the unit-test output that cover the rendered pages.)
  • Contains Code coverage (provide a link to the product’s code)
• Tugboat environment is prepped and added to collab cycle ticket
• PM is tagged to update this info on the collab cycle ticket at least 5 days before staging review

[xiongjaneg]

@mmiddaugh @jilladams Putting back in backlog, given the postponement of stating review

[davidmpickett]

@eselkin I marking this ticket as blocked by the other VBA test tickets. I assume the tests need to be created before the overall test plan can be written up. Let me know if I'm wrong

• SPIKE: Document the state of VBA Regional Office testing and prep for Staging Review #15223
• Front End testing for VBA Facility Service content type #14943
• Front End testing for regional subsections for VBA Service Region #14927

[davidmpickett]

marking as dupe with #15223