1.15 - Template Test Plans and 1.16 - Template Test Scripts

[nvcllns]

Work Request

Preparing for Testing

Rationale: Users of the ReportStream ETOR Intermediary Solution will expect to receive instruction on which scenarios will be in scope for end-user testing and associated supporting materials. The first recommended step is begin brainstorming an initial list of test scenarios in alignment with the MVP requirements and scenarios we know will be reflected in practice based on human-centered design interviews, feedback from APHL, and other sources. Ultimately, sites should receive ‘scripts’ that details the requested data element inputs, expected system behavior, and anticipated outputs for each scenario.

Testing plans should also be informed by any site-level requirement of CLIA documentation or internal production-level approvals.

Site partners will need to perform some level of ‘localization’ of test plans and scripts to make them appropriate for their specific EHR instance or NBS LIMS instance.

Non-exhaustive initial list of test scenarios to consider for user acceptance testing: • Name change of infant from “Baby Girl” to assigned name • Order cancelation (If in scope?) • Various scenarios related to missing/invalid required fields (what error state will be invoked? What error message will be returned?) • Error state due to unavailability of ReportStream platform (what error message will be returned? What action is then expected of sending system?) • Handling of unsolicited results

Anticipated Ticket Size: Large

Anticipated Urgency Level: Suggesting Low (initiate in sprint after next?)

Other Notes

These TA Outputs are reflected in 1.15 and 1.16 within the NBS ETOR ReportStream Technical Assistance Development Framework and working drafts and final copies can be uploaded or linked at 1.15 Template Test Plans and 1.16 Template Test Scripts.

[JohnNKing]

I'm thinking this will overlap heavily with https://github.com/CDCgov/trusted-intermediary/issues/559. Recommend re-assessing after #559 is completed; new stories may be needed to cover additional scope.

[nvcllns]

That's fine! But calling out that 559 looks to be exclusive to orders,,,,so where shall we park ideas/critieria for testing beyond orders in the interim?

[JohnNKing]

That's fine! But calling out that 559 looks to be exclusive to orders,,,,so where shall we park ideas/critieria for testing beyond orders in the interim?

+1 -- I think right here is perfect for those ideas.

I was thinking we'll need future stories for:

• Results test scenarios
• Testing failure scenarios
• Support Documentation
  • Testing guide
  • Re-usable template for other states
  • CLIA-specific processes
  • Production verification process

[JohnNKing]

Discussed during Research Collab today. We need to draft epics and stories needed for:

1. Template for HCO & PHL can use for testing (EHR => LIMS and LIMS => EHR)
2. End to end testing scenarios that can be incorporated into TI and ReportStream
3. Game day scenarios for testing connectivity failures and recovery process

[JohnNKing]

Regarding the first item above, this aligns well with this story that we've refined and moved to "In Progress": #965

[JohnNKing]

I've also created stories for CA and LA: #1110 & #1111