Practice Site · QA Lab
Insurance Claims Practice App.
Practise workflow-heavy QA testing using an insurance claims application. Test claim creation, policy lookup, customer details, incident details, document upload, claim status transitions, decisions, notes, history and notification behaviour.
Intermediate1–2 hoursDomain workflowAutomation friendlyManualWorkflowFile UploadRole Testing
Scenarios
28
Seeded bugs
10
Best for
Workflow testing · Role-based testing · File upload
Test data
✓ Included
Answer guide
✓ Included
On this page18 sections
// WHAT YOU'LL PRACTISE
- Multi-step form testing
- Draft and resume flows
- Required field validation
- Date validation
- File upload testing
- Claim lifecycle testing
- Status transition testing
- Role-based access testing
- Internal notes and customer visibility
- Notification testing
- Audit history validation
// WHO THIS IS FOR
Manual QA engineers practising business workflow testingTesters working with insurance, claims or case-management systemsQA learners practising complex formsAutomation testers building end-to-end workflow testsInterview candidates preparing domain examples
// APP MODULES
Policy lookupClaim creationCustomer detailsIncident detailsDocument uploadClaim summaryClaim submissionClaim statusClaim reviewClaim decisionClaim notesClaim historyEmail notificationsCustomer portalClaims handler portal
// TEST DATA
Ready-to-use data for positive, negative and boundary scenarios.
Roles
CustomerClaims handler
Policies
Active policyExpired policy
Documents
Supported (.pdf / .jpg / .png)Unsupported (.exe renamed to .pdf)
Claims
Draft claimSubmitted claimRejected claim
// PRACTICE MISSIONS
Small, focused tasks to warm up before the full lab.
45 mins
Test the document upload workflow
File upload testing, workflow testing
→ Upload test matrix, bug reports40 mins
Move a claim through its status workflow
State transition testing, business rules
→ Workflow transition test cases30 mins
Test role access to internal notes
Role-based access testing
→ Role-permission matrix, bug report// TEST SCENARIOS
Claim creation
- Create a new claim with valid details.
- Search for an existing policy.
- Attempt claim creation with an invalid policy number.
- Save the claim as a draft.
- Resume a draft claim.
- Submit the claim without required fields.
- Enter a future incident date.
- Enter an incident date before the policy start date.
Document upload
- Upload a supported document type.
- Upload an unsupported document type.
- Upload a file above the size limit.
- Upload multiple documents.
- Remove an uploaded document.
- Preview an uploaded document.
- Verify the uploaded document appears in the claim summary.
Claim lifecycle
- Submit a claim successfully.
- Verify the status changes to Submitted.
- Request more information.
- Add a customer response.
- Approve a claim.
- Reject a claim.
- Reopen a claim if allowed.
- Verify invalid status transitions are blocked.
Roles and notifications
- Verify a customer cannot see internal notes.
- Verify a claims handler can add internal notes.
- Verify the claim history records all actions.
- Verify the customer receives a claim-submission email.
- Verify duplicate notifications are not sent.
// MATRICES
Workflow transition matrix
| From status | Allowed next | Must be blocked |
|---|---|---|
| Draft | Submitted | Approved / Rejected |
| Submitted | Under review, More info requested | Approved without review |
| More info requested | Under review | — |
| Under review | Approved, Rejected | — |
| Rejected | — (terminal) | Approved |
| Approved | — (terminal) | Re-approved / silently edited |
Role permission matrix
| Capability | Customer | Claims handler |
|---|---|---|
| View claim status | Yes | Yes |
| Upload documents | Yes | Yes |
| View internal notes | No | Yes |
| Add internal notes | No | Yes |
| Approve / reject claim | No | Yes |
File upload test matrix
| File | Expected result |
|---|---|
| report.pdf (real PDF) | Accepted |
| photo.jpg / photo.png | Accepted |
| malware.exe renamed report.pdf | Rejected (content, not extension) |
| 0-byte file | Rejected |
| File over the size limit | Rejected with a clear message |
// SEEDED BUGS
This app seeds 10 bugs. Try to find them first, then reveal the answer guide to check your findings — each row links to its Common Bugs category.
| Bug | Example | Skill | Common Bugs |
|---|---|---|---|
| Draft data lost | A returning user sees an empty form | Workflow testing | Data bugs → |
| MIME validation bug | A .exe renamed as .pdf is accepted | File testing | File upload bugs → |
| Status transition bug | A rejected claim can be approved | Business rules | Data bugs → |
| Duplicate email | A customer receives the same email twice | Notification testing | Notification bugs → |
| Missing audit log | A decision is not recorded in history | Audit validation | Data bugs → |
| Role bug | A customer can view internal notes | Authorization testing | Permission bugs → |
| Date bug | A future incident date is accepted | Date validation | Time & date bugs → |
| Policy bug | A claim is allowed for an expired policy | Business rule testing | Data bugs → |
| Upload display bug | A deleted file still appears on the summary | Data consistency | File upload bugs → |
| Required field bug | A claim submits without an incident location | Form validation | UI bugs → |
An .exe renamed to .pdf is accepted as a claim documentSeverity: HighPriority: High
Steps to reproduce
- Open a claim and go to document upload
- Rename an executable to evidence.pdf
- Upload the file
Expected: Upload is rejected — the file is not really a PDF.
Actual: The file is accepted; only the extension was checked.
// REGRESSION CHECKLIST
The checks that would catch every seeded bug — reveal once you've done your own pass.
- A saved draft survives a refresh
- Only supported file types are accepted (content, not extension)
- A rejected claim cannot be approved later
- Customers cannot see internal handler notes
- A claim cannot be filed against an expired policy
- Every decision is recorded in claim history
// MANUAL & AUTOMATION TASKS
Manual testing tasks
- Create test cases for claim creation.
- Test draft save and resume.
- Test file upload positive and negative cases.
- Test claim status transitions.
- Test customer vs claims-handler permissions.
- Verify notification and audit-history behaviour.
- Report workflow bugs with their business impact.
Automation tasks
- Automate valid claim submission.
- Automate required-field validation.
- Automate document-upload checks.
- Automate a claim status transition.
- Automate role-visibility checks.
- Automate notification-trigger verification where practical.
// INTERVIEW MODE
Reflection questions to rehearse how you'd talk through testing this app.
How would you test a multi-step claim form with save-and-resume?
How do you build a status-transition matrix for a workflow?
How would you test role-based visibility of internal notes?
What does a thorough file-upload test matrix include?
How do you verify an audit trail records every decision?
// WHAT YOU'LL PRODUCE
Workflow test casesRole-permission testsUpload test matrix
// SUGGESTED TOOLS
PlaywrightCypressSeleniumPostmanREST AssuredMailosaur / Mailtrap-style email testingBrowser DevTools
// AUTOMATION STARTERS
Fork a ready-made framework to automate this app — each sample ships with setup, CI and reporting.
// DOWNLOADS
// PORTFOLIO WRITE-UP
Use this as a starting point for your CV, LinkedIn or portfolio — swap in the tools and findings that are actually yours.
I tested an insurance claims practice app covering policy lookup, claim creation, draft save, document upload, claim status transitions, role-based access, notifications and audit history. I focused on workflow rules, file validation, permissions and business-critical edge cases.
// NEXT RECOMMENDED APP
Accessibility lab
Continue →Accessibility Practice App
Practise keyboard testing, focus management, accessible forms, modals, colour contrast, ARIA mistakes and screen reader basics on components with seeded a11y issues.