Test Case Register — My Accidents (MA)¶
Coverage Summary¶
| Total TCs | Automated | Manual | Pending | Coverage % |
|---|---|---|---|---|
| 30 | 0 | 0 | 30 | 0% |
| Critical | High | Medium | Low |
|---|---|---|---|
| 16 | 6 | 7 | 1 |
Test Case Table¶
1. Menu & Access Control¶
| TC ID | Test Scenario | AC | Jira | Priority | Coverage | Cucumber Tag | Preconditions | Test Data | High-level Steps | Expected Result | Status | Note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TC-MA-001 | Logged-in user opens the Activities menu | AC-MA-01 | RC-111 | 🔴 Critical | 🔵 Pending | @TC-MA-001 |
User is logged in | — | 1. Tap Activities | The Activities page displays with the menu list: My accidents, Digital cost estimates, Car rental cost estimates (each with its description line) | ⬜ Not Run | |
| TC-MA-002 | Guest user is blocked from Activities / My Accidents | AC-MA-02 / BR-MA-01 | RC-111 | 🔴 Critical | 🔵 Pending | @TC-MA-002 |
User is not logged in (guest) | — | 1. Attempt to open Activities or My Accidents directly (e.g. via deep link or nav) | Access is denied and the user is prompted to log in before the page is shown | ⬜ Not Run | |
| TC-MA-003 | Back button on Activities menu returns to Home | AC-MA-03 | RC-111 | 🟡 Medium | 🔵 Pending | @TC-MA-003 |
User is on the Activities menu page | — | 1. Tap the Back button in the top app bar | The user is returned to the Home page | ⬜ Not Run |
2. Reported Accidents Tab (Tab 1)¶
| TC ID | Test Scenario | AC | Jira | Priority | Coverage | Cucumber Tag | Preconditions | Test Data | High-level Steps | Expected Result | Status | Note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TC-MA-004 | Reported accidents tab shows the empty state | AC-MA-04 | RC-111 | 🔴 Critical | 🔵 Pending | @TC-MA-004 |
Logged-in user has zero reported accidents | — | 1. Navigate to My Accidents 2. Open the Gemeldete Unfälle (Reported accidents) tab |
A centered car icon and the text "No Accidents reported" (DE: "Keine Unfälle gemeldet") are displayed | ⬜ Not Run | |
| TC-MA-005 | Reported accident is shown as a completed card | AC-MA-05 | RC-111 | 🔴 Critical | 🔵 Pending | @TC-MA-005 |
Logged-in user has ≥1 reported (completed) accident | Vehicle: VOLKSWAGEN Atlas SEL Premium R-Line (2023) | 1. Open the Reported accidents tab 2. Inspect the accident card |
Card shows a "COMPLETED" (DE: "ABGESCHLOSSEN") status badge, the vehicle brand/model/year, and a 3-dot context-menu icon | ⬜ Not Run | UI ref: 01_Features/accident/wa_my_accident/screens/Screenshot 2026-08-06 at 10.45.16.png |
| TC-MA-006 | 3-dot menu opens the reported-accident action sheet | AC-MA-06 | RC-111 | 🟠 High | 🔵 Pending | @TC-MA-006 |
A reported-accident card is visible | — | 1. Tap the card's 3-dot icon | A bottom sheet opens with "View accident" (eye icon), "Delete accident" (trash icon, red text), and "Cancel" | ⬜ Not Run | |
| TC-MA-007 | Viewing a reported accident opens the final submission screen | AC-MA-07 | RC-111 | 🔴 Critical | 🔵 Pending | @TC-MA-007 |
A reported-accident (COMPLETED) card is visible | — | 1. Tap the card row (or select View accident from its action sheet) | The "Thank you, All steps are now completed" screen for that accident displays, showing "4 OF 4 STEPS COMPLETED" with all 4 steps checked | ⬜ Not Run | |
| TC-MA-008 | Deleting a reported accident succeeds | AC-MA-08 | RC-111 | 🔴 Critical | 🔵 Pending | @TC-MA-008 |
A reported-accident card's action sheet is open | — | 1. Tap Delete accident | The accident is removed from the Reported accidents list And the message "Delete accident successfully" (DE: "Unfall erfolgreich gelöscht") is shown |
⬜ Not Run | |
| TC-MA-009 | Cancel dismisses the reported-accident action sheet without changes | AC-MA-10 | RC-111 | 🟡 Medium | 🔵 Pending | @TC-MA-009 |
A reported-accident card's action sheet is open | — | 1. Tap Cancel | The bottom sheet closes and the accident is unchanged in the list | ⬜ Not Run |
3. Saved Accidents Tab (Tab 2 — Drafts)¶
| TC ID | Test Scenario | AC | Jira | Priority | Coverage | Cucumber Tag | Preconditions | Test Data | High-level Steps | Expected Result | Status | Note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TC-MA-010 | Saved (draft) accident is shown as a collapsed card | AC-MA-11 | RC-111 | 🔴 Critical | 🔵 Pending | @TC-MA-010 |
Logged-in user has ≥1 saved accident | Vehicle: ABT ACL2 Concept (1993), status NEU; ABT ACL2 Concept (1991), status AUSSTEHEND | 1. Open the Gespeicherte Unfälle (Saved accidents) tab 2. Inspect the cards |
Each card shows a "NEW" or "PENDING" (DE: "NEU" / "AUSSTEHEND") status badge, vehicle brand/model/year, an expand chevron, and a 3-dot context-menu icon | ⬜ Not Run | UI ref: 01_Features/accident/wa_my_accident/screens/Screenshot 2026-08-06 at 10.44.56.png |
| TC-MA-011 | Expanding a saved-accident card reveals the progress timeline | AC-MA-12 | RC-111 | 🟠 High | 🔵 Pending | @TC-MA-011 |
A saved-accident card is collapsed | — | 1. Tap the card's expand chevron | The card expands showing a vertical timeline of the 4 reporting steps: Accident details, Accident Photos, Vehicle part details, Capture vehicle doc. | ⬜ Not Run | |
| TC-MA-012 | Completed vs. pending steps are visually distinguished | AC-MA-13 | RC-111 | 🟡 Medium | 🔵 Pending | @TC-MA-012 |
A saved-accident card is expanded, with 2 of 4 steps completed | Step 1 completed at "DEC 07, 1:06:00 PM" | 1. View the expanded progress timeline | Completed steps show a green checkmark and completion timestamp; pending steps show a disabled/gray state | ⬜ Not Run | |
| TC-MA-013 | Continue report resumes the flow at the next incomplete step | AC-MA-14 | RC-111 | 🔴 Critical | 🔵 Pending | @TC-MA-013 |
A saved-accident card is expanded with step 2 as the next incomplete step | — | 1. Tap Continue report inside the expanded card | The report-accident flow resumes at step 2 for that accident | ⬜ Not Run | |
| TC-MA-014 | 3-dot menu opens the saved-accident action sheet | AC-MA-15 | RC-111 | 🟠 High | 🔵 Pending | @TC-MA-014 |
A saved-accident card is visible | — | 1. Tap the card's 3-dot icon | A bottom sheet opens with "Continue report" (document icon), "Delete saved accident" (trash icon, red text), and "Cancel" | ⬜ Not Run | |
| TC-MA-015 | Deleting a saved accident succeeds | AC-MA-16 | RC-111 | 🔴 Critical | 🔵 Pending | @TC-MA-015 |
A saved-accident card's action sheet is open | — | 1. Tap Delete saved accident | The draft is removed from the Saved accidents list And the message "Delete accident successfully" (DE: "Unfall erfolgreich gelöscht") is shown |
⬜ Not Run |
4. Negative — Delete Failures¶
| TC ID | Test Scenario | AC | Jira | Priority | Coverage | Cucumber Tag | Preconditions | Test Data | High-level Steps | Expected Result | Status | Note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TC-MA-016 | Deleting a reported accident fails | AC-MA-09 | RC-111 | 🟠 High | 🔵 Pending | @TC-MA-016 |
A reported-accident card's action sheet is open Delete request will return a server/system error (mocked failure) |
— | 1. Tap Delete accident | The accident remains in the Reported accidents list And the message "Can't delete this accident." (DE: "Dieser Unfall konnte nicht gelöscht werden.") is shown |
⬜ Not Run | [DEP] requires mocked failure response |
| TC-MA-017 | Deleting a saved accident fails | AC-MA-17 | RC-111 | 🟠 High | 🔵 Pending | @TC-MA-017 |
A saved-accident card's action sheet is open Delete request will return a server/system error (mocked failure) |
— | 1. Tap Delete saved accident | The draft remains in the Saved accidents list And the message "Can't delete this accident." (DE: "Dieser Unfall konnte nicht gelöscht werden.") is shown |
⬜ Not Run | [DEP] requires mocked failure response |
5. Final Submission Screen — Content¶
| TC ID | Test Scenario | AC | Jira | Priority | Coverage | Cucumber Tag | Preconditions | Test Data | High-level Steps | Expected Result | Status | Note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TC-MA-018 | Final submission screen displays on completion of all 4 steps | AC-MA-18 | RC-111 | 🔴 Critical | 🔵 Pending | @TC-MA-018 |
User has just completed the 4th (last) reporting step for an accident | — | 1. Complete the final (4th) reporting step | Screen shows title "Thank you, All steps are now completed", "4 OF 4 STEPS COMPLETED", and all 4 steps green-checkmarked | ⬜ Not Run | UI ref: 01_Features/accident/wa_my_accident/screens/Screenshot 2026-08-06 at 10.45.55.png |
| TC-MA-019 | Each completed step can be opened for review | AC-MA-19 | RC-111 | 🟡 Medium | 🔵 Pending | @TC-MA-019 |
User is on the final submission screen for a completed accident | — | 1. Tap the "Accident details" step row | That step's captured details open for review | ⬜ Not Run | |
| TC-MA-020 | Added emails appear as removable chips | AC-MA-22 | RC-111 | 🟡 Medium | 🔵 Pending | @TC-MA-020 |
User is on the final submission screen with the email input focused | email: qa.tester1@example.com |
1. Enter the email address 2. Tap Add |
The email appears as a chip below the input, with an 'x' control to remove it | ⬜ Not Run | |
| TC-MA-021 | Removing the only email chip re-blocks Send report | AC-MA-23 | RC-111 | 🟡 Medium | 🔵 Pending | @TC-MA-021 |
Exactly one email chip added; Privacy Policy checkbox checked | email: qa.tester1@example.com |
1. Tap the 'x' on the email chip | The chip is removed And Send report becomes unavailable again (zero emails) |
⬜ Not Run | |
| TC-MA-022 | Multiple emails can be added before sending | AC-MA-22 | RC-111 | ⚪ Low | 🔵 Pending | @TC-MA-022 |
User is on the final submission screen | emails: qa.tester1@example.com, qa.tester2@example.com, qa.tester3@example.com |
1. Add all 3 email addresses one by one | All 3 emails appear as separate chips, each independently removable | ⬜ Not Run |
6. Send Report — Validation (Decision Table: Privacy checkbox × Email count)¶
| TC ID | Test Scenario | AC | Jira | Priority | Coverage | Cucumber Tag | Preconditions | Test Data | High-level Steps | Expected Result | Status | Note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TC-MA-023 | Send report blocked — privacy unchecked, no email | AC-MA-20 | RC-111 | 🔴 Critical | 🔵 Pending | @TC-MA-023 |
User is on the final submission screen | Privacy checkbox: unchecked; Emails: none | 1. Attempt to tap Send report | Report is not submitted; Send report is unavailable/blocked | ⬜ Not Run | |
| TC-MA-024 | Send report blocked — privacy checked, no email | AC-MA-20 | RC-111 | 🔴 Critical | 🔵 Pending | @TC-MA-024 |
User is on the final submission screen | Privacy checkbox: checked; Emails: none | 1. Attempt to tap Send report | Report is not submitted; Send report is unavailable/blocked | ⬜ Not Run | |
| TC-MA-025 | Send report blocked — privacy unchecked, has email | AC-MA-20 | RC-111 | 🔴 Critical | 🔵 Pending | @TC-MA-025 |
User is on the final submission screen | Privacy checkbox: unchecked; Emails: qa.tester1@example.com |
1. Attempt to tap Send report | Report is not submitted; Send report is unavailable/blocked | ⬜ Not Run | |
| TC-MA-026 | Send report succeeds — privacy checked and ≥1 email | AC-MA-21 | RC-111 | 🔴 Critical | 🔵 Pending | @TC-MA-026 |
User is on the final submission screen | Privacy checkbox: checked; Emails: qa.tester1@example.com |
1. Tap Send report | The report submission succeeds | ⬜ Not Run |
7. Business Rules & Data Integrity¶
| TC ID | Test Scenario | AC | Jira | Priority | Coverage | Cucumber Tag | Preconditions | Test Data | High-level Steps | Expected Result | Status | Note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TC-MA-027 | Deleted accident is soft-deleted, not permanently removed | BR-MA-02 | RC-111 | 🔴 Critical | 🔵 Pending | @TC-MA-027 |
A reported or saved accident exists and is deleted via the UI (see TC-MA-008 / TC-MA-015) | — | 1. Delete the accident via the UI 2. Inspect the underlying record (DB / admin API) |
The record is excluded from the active list And still exists in storage with a soft-delete marker (not physically removed) |
⬜ Not Run | [DATA] requires backend/DB access to verify |
| TC-MA-028 | Final submission screen shows only "Send report", no "Save it for later" | BR-MA-04 | RC-111 | 🔴 Critical | 🔵 Pending | @TC-MA-028 |
User is on the final submission screen for a completed accident | — | 1. Inspect the action buttons on the final screen | Only the Send report primary button is present And no "Save it for later" button is shown |
⬜ Not Run | Regression check — verifies removal per ticket comment amendment |
| TC-MA-029 | Sending a report does not email a PDF yet (deferred) | BR-MA-05 | RC-111 | 🟡 Medium | 🔵 Pending | @TC-MA-029 |
Privacy checkbox checked; ≥1 email added | email: qa.tester1@example.com |
1. Tap Send report 2. Check the recipient mailbox / outbound-email log |
The submission succeeds And no PDF report email is sent (feature intentionally deferred) |
⬜ Not Run | [DATA] requires mailbox/log access to verify absence |
8. State Transition / Integration¶
| TC ID | Test Scenario | AC | Jira | Priority | Coverage | Cucumber Tag | Preconditions | Test Data | High-level Steps | Expected Result | Status | Note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TC-MA-030 | Completing the last pending step moves the accident from Saved to Reported | — | RC-111 | 🟠 High | 🔵 Pending | @TC-MA-030 |
A saved accident has 3 of 4 steps completed | — | 1. Tap Continue report and complete the 4th (last) step | The accident no longer appears in the Saved accidents tab And now appears in the Reported accidents tab with status "COMPLETED" |
⬜ Not Run | Inferred integration behaviour — not an explicit AC; confirm with PO |
Gherkin Mapping (Automated TCs only)¶
No TCs are automated yet — all 30 are 🔵 Pending. Add
.featurescenarios here as automation is implemented.