QA Automation/Tester Healthrules

Member Preferences EPMO UAT Test Coordinators: Business Testing Resources Needed

Business testing resources are needed for 2 full-time positions. Under certain circumstances, it may be possible to use one resource. The timeline is from June through mid-July (approx. 6 weeks) per the current project plan.

Duties starting approx. 3 weeks prior to scheduled UAT (Early June) include:

• Meet with the project team, and with business users/SMEs - Determine the exact nature of "member preference" data to be entered and/or extracted - Confirm methodology for data entry and retrieval
• If two resources are available, duties will be divided to ensure:
• Document test scenarios
• Design test cases. Include:
• Entering new members, and documenting "member preference" values.
• Standard end-to-end tests
• Negative tests/invalid values/etc.
• Conflicting changes to fields entered through different sources – to test the hierarchy
• Retrieve test members in all formats (customer service, reports, mailed fulfilments, outbound files to ancillary vendors, etc.)
• Modifying members
• Repeat the above tests for member modifications
• Review QA team's (technical) tests
• Check if we can leverage any of that team's test data
• Check for test case overlaps/gaps
• If time permits, enter test cases into Jira
• Meet with assigned technical assistance resource to confirm their ability to support test cases – including:
• Modify batch input (e.g. 834s) for data entry
• Run batch jobs to emulate production
• Extract file-based data (e.g. data destined for ancillary vendors)
• Coordinate business owners/SMEs - Time scheduling - Forward business owners the full suite of information on tests to be conducted, to enable them to prepare.
• Validate test-data to be entered (create 2 members for each CCA product.)
• Scheduled UAT Testing (Late June to mid-July) EPMO business test coordinators will not conduct the tests – that will be done by business users. The UAT team will coordinate UAT sessions with business owners/SMEs – including the following activities:
• Validate input data
• Monitor business users as they execute test cases
• Liaise with and coordinate technical assists as needed (run batch processes, etc.)
• Confirm that users can retrieve results
• Ensure users are satisfied with test results
• Document results
• Coordinate defect resolution and re-testing as appropriate
• Update requirements traceability matrix (RTM)
• Please refer to the attached "UAT Approach" slide-deck for a high-level overview of the UAT approach.
• Skillsets EPMO business testers will not conduct the tests – that will be done by business users. But in order to coordinate, they should possess:
• Solid knowledge of healthcare payer practices
• Solid knowledge of CCA's processes for entry, processing, and retrieval of enrollment-related data
• Ability to communicate confidently and effectively with expert-level CCA staff
• Ability to coordinate
• Ability to document
• Resource considerations: The ideal staffing model would include 2 full-time resources. If only one resource is made available, then:
• That person would need to be relatively senior and extremely capable.
• Some of the coordination/administrative activities would need to be conducted by Jane Mitchell (PM) and Duncan Glenday (EPMO Quality Lead)
• The UAT timeline will probably be impacted.
• If an outsider is hired to address the Member Preferences UAT, then adequate ramp-up time will need to be accommodated – both, on the schedule and in the budget. A resource who is already familiar with CCA's systems and personnel would eliminate that concern.
• Current plans are for the PBM program to onboard testing resources in Q3 and Q4. It might behoove CCA to assign resources to this Member Preferences Project, who could then roll directly onto PBM – this trimming the ramp-up cost for both programs.