Case study 04 / Optum
Turning requirements into reliable test coverage.
Connecting business requirements to functional testing, integration checks, and database validation.
The challenge
Member enrollment and benefits workflows required coverage tied to requirements, along with validation of data exchanged between systems.
My contribution
- Automated and manually verified member enrollment and benefits workflows with Selenium WebDriver and WebdriverIO.
- Mapped eligibility and claims test cases to requirements in qTest to make coverage gaps visible before release.
- Validated member and transaction records directly in MySQL.
- Verified REST and SOAP integrations in Postman, supported functional and regression testing, and worked with developers to confirm fixes.
The outcome
Requirements connected to test evidence
The focus was traceable coverage, correct stored records, and reliable integrations across payer workflows.
Engineering example
A representative enrollment review
SYNTHETIC EXAMPLE — NO MEMBER DATA Requirement Enrollment changes must persist correctly UI check Submitted change is reflected in the workflow API check Response contains the expected fields Data check Stored record matches the submitted change Regression Related benefits behavior remains consistent
Independent illustration of the approach. No proprietary client code or production data.
The takeaway
Traceability matters when several workflows share member data. Linking requirements to test cases helps identify what needs another look when a change arrives.
Next case study