Test Users
- Removes the need to request test user/SAML for every issue reported
- Expedites HealthSparq’s triage process
- Facilitates reproduction steps
- Provides context to troubleshoot & validate issue
- Improves alignment between HealthSparq and your team
What Do Test Users Represent?
- Validates plan and brand/tenant of use case
- Confirms network/plan being used
- Confirms alpha prefix for communication with BCBSA APIs
- Provides test user information for benefit response validation (as appropriate for test case)
Ex. Not seeing National Providers when performing a PCP search out of area for a student dependent:
As authenticated user X, when I change my location to Missoula, MT, select the Doctors by specialty tile and search for PCPs no results are returned
Test Scenarios
- Expedites HealthSparq’s triage process
- Facilitates reproduction steps
- Provides context to troubleshoot & validate issue
- Understanding each plan’s unique testing needs
- Test cases for provider searches
- public and/or authenticated searches
- Test cases for downstream processes (CLNR, NCCT, etc)
- Improves alignment between HealthSparq and your team
What Do Test Scenarios Represent?
- Specific use case being tested/validated
- Reproduction steps
- Clearly defined expected results
- Blueprint to troubleshoot the issue
Provider Search:
Ex. Not seeing National Providers when performing a PCP search out of area for a student dependent :
As authenticated user X, when I change my location to Missoula, MT, and search Doctors by specialty, PCPs {Bob Family-Practice,MD, Jane PCP} should return is search results
Cost search:
Ex. Not seeing expected CLNR rate:
As authenticated user X, when I change my location to Missoula, MT, select the cost tile, and search for negotiated rates using {billingcode} I see the negotiated rate of {negotiatedrate{} for provider {Dr. Bob Family-Practice}
