Test Case Register — Accident Assistant (AA)¶
Coverage Summary¶
| Total TCs | Automated | Manual | Pending | Coverage % |
|---|---|---|---|---|
| 67 | 0 | 0 | 67 | 0% |
| Critical | High | Medium | Low |
|---|---|---|---|
| 23 | 25 | 18 | 1 |
Test Case Table¶
1. Entry & Vehicle Selection¶
| TC ID | Test Scenario | AC | Jira | Priority | Coverage | Cucumber Tag | Preconditions | Test Data | High-level Steps | Expected Result | Status | Note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TC-AA-001 | Starting Accident Assistance shows the user's vehicle list | AC-AA-01 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-001 |
User is logged in, on the Home page, with ≥1 registered vehicle | — | 1. Tap Accident Assistance (Unfallhilfe) | The "Report Accident" flow starts and the user's existing vehicle list is displayed | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 11.14.49.png |
| TC-AA-002 | User can add a new vehicle from the vehicle-selection screen | AC-AA-02 | RC-110 | 🟡 Medium | 🔵 Pending | @TC-AA-002 |
User is on the vehicle-selection screen | — | 1. Choose the add-new-vehicle option instead of an existing vehicle | The add-vehicle flow opens | ⬜ Not Run | |
| TC-AA-003 | Selecting a vehicle navigates to the Overview page | AC-AA-03 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-003 |
User is on the vehicle-selection screen with ≥1 vehicle listed | Vehicle: VOLKSWAGEN Atlas SEL Premium R-Line (2023) | 1. Select the vehicle 2. Tap Report accident |
The user is navigated to the Overview page | ⬜ Not Run |
2. Overview Page¶
| TC ID | Test Scenario | AC | Jira | Priority | Coverage | Cucumber Tag | Preconditions | Test Data | High-level Steps | Expected Result | Status | Note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TC-AA-004 | Overview page shows the outline of all report steps | AC-AA-04 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-004 |
User has just navigated to the Overview page | — | 1. View the Overview page | An outline of the steps required to report the damage is displayed (e.g. Accident details, Accident photos, vehicle documents, vehicle part details) | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 11.14.49.png |
| TC-AA-005 | Next on the Overview page opens Step 1: Accident Details | AC-AA-05 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-005 |
User is on the Overview page | — | 1. Tap Next | The user is navigated to Step 1: Accident Details | ⬜ Not Run |
3. Step 1 — Date/Time & Location¶
| TC ID | Test Scenario | AC | Jira | Priority | Coverage | Cucumber Tag | Preconditions | Test Data | High-level Steps | Expected Result | Status | Note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TC-AA-006 | User selects the date and time the accident happened | AC-AA-06 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-006 |
User is on the Step 1: Accident Details page | Datum: today's date; Uhrzeit: 14:30 | 1. Select a value for Datum 2. Select a value for Uhrzeit |
The selected date and time are set on the form | ⬜ Not Run | |
| TC-AA-007 | User manually types the accident location | AC-AA-07 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-007 |
User is on the Step 1: Accident Details page | Location: Bussenstraße, 70184 Stuttgart, Germany |
1. Type into "Wo ist der Unfall passiert?" | The typed value is set as the location | ⬜ Not Run | |
| TC-AA-008 | Map icon opens a map view auto-detecting current location | AC-AA-08 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-008 |
User is on the Step 1: Accident Details page Device location services enabled |
— | 1. Tap the map icon next to the location field | A map view opens and auto-detects/centers on the user's current location | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 11.15.19.png |
| TC-AA-009 | User can adjust the pin or search for a different location on the map | AC-AA-09 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-009 |
The map view is open | Search query: Aussichtspunkt Straußstaffel |
1. Drag the map pin to a new spot, or search for an address and select a result | The map updates to reflect the newly selected location | ⬜ Not Run | |
| TC-AA-010 | Confirming a map location populates the location field | AC-AA-10 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-010 |
The map view is open with a location selected | — | 1. Tap Next / confirm on the map view | The map closes and "Wo ist der Unfall passiert?" is populated with the confirmed address | ⬜ Not Run |
4. Step 1 — Incident Type & Proceed Gate¶
| TC ID | Test Scenario | AC | Jira | Priority | Coverage | Cucumber Tag | Preconditions | Test Data | High-level Steps | Expected Result | Status | Note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TC-AA-011 | Incident-type field shows the 4 defined options | AC-AA-11 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-011 |
User is on the Step 1: Accident Details page | — | 1. Tap "Was ist passiert?" | Dropdown lists exactly: "Unfall mit weiteren Beteiligten", "Unfall ohne weitere Beteiligte", "Zusammenstoß mit einem Tier", "Sonstiger Schaden" | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 11.15.04.png |
| TC-AA-012 | Selecting an incident type sets the field value | AC-AA-12 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-012 |
The incident-type dropdown is open | Selected: "Unfall mit weiteren Beteiligten" | 1. Select one option from the dropdown | The dropdown closes and the field displays the selected option | ⬜ Not Run | |
| TC-AA-013 | Proceed is unavailable while the Step 1 form is incomplete | AC-AA-13 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-013 |
User is on the Step 1: Accident Details page with the form blank | Leave each field empty in turn: (a) Datum only filled, (b) + Uhrzeit filled, (c) + location filled, incident type still empty | 1. Fill the form partially, one field short of complete, for each combination (a)-(c) 2. Attempt to tap Proceed |
Proceed remains disabled/unavailable in every case; the form is not submitted | ⬜ Not Run | Equivalence classes: any required field missing |
| TC-AA-014 | Proceed on a complete Step 1 form opens Parties Involved | AC-AA-14 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-014 |
Datum, Uhrzeit, location, and incident type are all filled | Incident type: "Unfall mit weiteren Beteiligten" | 1. Tap Proceed | The user is navigated to the Parties Involved (Unfallbeteiligte) section — not a blank page | ⬜ Not Run |
5. Parties Involved¶
| TC ID | Test Scenario | AC | Jira | Priority | Coverage | Cucumber Tag | Preconditions | Test Data | High-level Steps | Expected Result | Status | Note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TC-AA-015 | Parties Involved shows the add-parties prompt with a 5-person limit | AC-AA-15 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-015 |
User has just entered the Parties Involved section, no party added yet | — | 1. View the screen | A "Beteiligte hinzufügen" prompt with a "+" icon is shown, stating up to 5 people can be added | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 11.15.37.png |
| TC-AA-016 | "+" opens the add-party form | AC-AA-16 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-016 |
User is on the Parties Involved section | — | 1. Tap the "+" icon | A new screen opens with a "Beteiligt als" field to enter the party's info | ⬜ Not Run | |
| TC-AA-017 | Selecting "PKW Fahrer" renders the driver-specific form | AC-AA-17 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-017 |
The add-party form is open | Beteiligt als: PKW Fahrer | 1. Select "PKW Fahrer" in "Beteiligt als" | Form renders: Kennzeichen (vehicle plate) + contact fields (Vorname, Nachname, Vorwahl, Telefonnummer, E-mail, Adresse) | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 11.15.04.png |
| TC-AA-018 | Selecting "Fußgänger" renders the pedestrian-specific form | AC-AA-18 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-018 |
The add-party form is open | Beteiligt als: Fußgänger | 1. Select "Fußgänger" in "Beteiligt als" | Form renders contact fields only (Vorname, Nachname, Vorwahl, Telefonnummer, E-mail) — no Kennzeichen field | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 11.15.37.png |
| TC-AA-019 | Adding a party returns to the list showing the new entry | AC-AA-19 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-019 |
The add-party form is filled with valid PKW Fahrer data | Kennzeichen: M-QM 83F34; Name: John Doe; City: München |
1. Fill the form 2. Tap Add |
User returns to the Parties Involved list; the new party appears with badge "PKW-Fahrer" and its summary details | ⬜ Not Run | |
| TC-AA-020 | Parties Involved enforces the 5-person maximum | AC-AA-20 / BR-AA-01 | RC-110 | 🟡 Medium | 🔵 Pending | @TC-AA-020 |
4 parties already added | 5th party: Fußgänger, Jane Doe | 1. Add a 5th party (should succeed) 2. Attempt to add a 6th party |
5th party is added successfully; the "+"/Add-party action becomes unavailable and a 6th party cannot be added | ⬜ Not Run | Boundary: 4 (allowed) → 5 (max reached) → 6 (blocked) |
| TC-AA-021 | User can proceed with zero parties when there are no other parties involved | AC-AA-21 | RC-110 | 🟡 Medium | 🔵 Pending | @TC-AA-021 |
Incident type selected in Step 1 was "Unfall ohne weitere Beteiligte"; no party added | — | 1. On the Parties Involved screen, without adding any party, tap Proceed | Step 1 completes without requiring any added party | ⬜ Not Run | |
| TC-AA-022 | Proceed on Parties Involved completes Step 1 and returns to Overview | AC-AA-22 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-022 |
≥1 party has been added on the Parties Involved screen | — | 1. Tap Proceed | Step 1 (Accident details) is marked "COMPLETED"; user is redirected to the Overview page, ready for Step 2 | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 11.15.37.png |
6. Business Rules & Regression¶
| TC ID | Test Scenario | AC | Jira | Priority | Coverage | Cucumber Tag | Preconditions | Test Data | High-level Steps | Expected Result | Status | Note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TC-AA-023 | Step 1 data persists and can be edited (save/edit API) | BR-AA-02 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-023 |
Step 1 has been completed and saved for an accident | — | 1. Re-open the saved/draft accident's Step 1 2. Edit the location and incident type 3. Save |
Previously entered values are pre-filled; edits are persisted via the API and reflected on re-open | ⬜ Not Run | [DATA] — verify via API/Swagger if UI re-entry is not yet available |
| TC-AA-024 | Proceed on Accident Details never leads to a blank page (regression) | BR-AA-03 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-024 |
Step 1 form fully completed | Repeat across incident types: with-parties, without-parties, animal collision, other damage | 1. Complete the Step 1 form for each incident type 2. Tap Proceed (Fortfahren) |
Parties Involved section renders correctly every time — never a blank/broken page | ⬜ Not Run | Regression for defect reported in ticket comment (2026-07-14) |
| TC-AA-025 | Switching party type re-renders the correct field set | BR-AA-04 | RC-110 | 🟡 Medium | 🔵 Pending | @TC-AA-025 |
The add-party form is open with "PKW Fahrer" selected and Kennzeichen partially filled | Switch to: Fußgänger | 1. Change "Beteiligt als" from PKW Fahrer to Fußgänger | The Kennzeichen field is removed from the form; only pedestrian contact fields remain, with no leftover vehicle-plate data submitted | ⬜ Not Run |
7. Step 2 — Accident Photo and Video (Capture Photos)¶
| TC ID | Test Scenario | AC | Jira | Priority | Coverage | Cucumber Tag | Preconditions | Test Data | High-level Steps | Expected Result | Status | Note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TC-AA-026 | Entering Step 2 shows the Accident Photo and Video checklist | AC-AA-23 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-026 |
Step 1 (Accident details) is COMPLETED | — | 1. From the Overview, open Accident Photo and Video | Checklist shows: Capture photos (IN PROGRESS, REQUIRED), Upload or record video (NOT STARTED, REQUIRED), Capture additional photos (NOT STARTED, OPTIONAL) | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 11.15.19.png |
| TC-AA-027 | Tapping "Capture photos" opens the damage-area selection diagram | AC-AA-24 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-027 |
User is on the Accident Photo and Video checklist | — | 1. Tap Capture photos | A vehicle diagram opens with "Wählen Sie die Bereiche aus, auf denen ihr Fahrzeug beschädigt ist" | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 11.15.37.png |
| TC-AA-028 | Damage-area screen lists all 9 vehicle zones | AC-AA-25 | RC-110 | 🟡 Medium | 🔵 Pending | @TC-AA-028 |
User is on the damage-area selection screen | — | 1. View the diagram | All 9 zones with camera icons shown: Vorne links, Vorne, Vorne rechts, Links, Dach, Rechts, Hinten links, Hinten, Hinten rechts | ⬜ Not Run | |
| TC-AA-029 | Tapping a zone's camera icon opens a guided camera | AC-AA-26 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-029 |
User is on the damage-area selection screen | Zone: Vorne | 1. Tap the camera icon on Vorne | Camera opens with translucent vehicle-outline overlay and prompt "Please take a closeup shot of the damage" | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 11.15.37.png |
| TC-AA-030 | Captured photo offers Re capture or Done before confirming | AC-AA-27 | RC-110 | 🟡 Medium | 🔵 Pending | @TC-AA-030 |
Guided camera is open for a zone | — | 1. Capture a photo | Preview shown with Re capture and Done options | ⬜ Not Run | |
| TC-AA-031 | Confirming a photo marks that zone as captured | AC-AA-28 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-031 |
Photo preview is shown with Re capture/Done | — | 1. Tap Done | Returns to the damage-area diagram; the captured zone is visually marked as done | ⬜ Not Run | |
| TC-AA-032 | "Done" on the zone-selection screen completes the Capture-photos requirement | AC-AA-29 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-032 |
≥1 zone photo captured | — | 1. Tap Done on the damage-area screen | Returns to checklist; "Capture photos" marked complete | ⬜ Not Run |
8. Step 2 — Video, Additional Photos & Completion Gate¶
| TC ID | Test Scenario | AC | Jira | Priority | Coverage | Cucumber Tag | Preconditions | Test Data | High-level Steps | Expected Result | Status | Note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TC-AA-033 | User can upload or record a video for damage documentation | AC-AA-30 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-033 |
User is on the Accident Photo and Video checklist | Sample video file / new recording | 1. Tap Upload or record video 2. Record or select a video |
Video is attached; "Upload or record video" marked complete | ⬜ Not Run | |
| TC-AA-034 | "Capture additional photos" is optional and can be skipped | AC-AA-31 | RC-110 | 🟡 Medium | 🔵 Pending | @TC-AA-034 |
"Capture photos" and "Upload or record video" already complete | — | 1. Do not interact with Capture additional photos 2. Proceed |
Step 2 completes; optional item remains NOT STARTED without blocking progress | ⬜ Not Run | |
| TC-AA-035 | Completing both required items marks Step 2 COMPLETED on the Overview | AC-AA-32 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-035 |
"Capture photos" and "Upload or record video" both complete | — | 1. Navigate back to the Overview | "Accident Photo and Video" shows COMPLETED | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 11.15.59.png |
| TC-AA-036 | Step 2 stays IN PROGRESS while a required item is missing | AC-AA-33 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-036 |
"Capture photos" complete; "Upload or record video" NOT done | — | 1. Navigate back to the Overview without completing the video | "Accident Photo and Video" still shows IN PROGRESS, not COMPLETED | ⬜ Not Run | Negative — completion gate |
9. Step 3 — Capture Vehicle Documents¶
| TC ID | Test Scenario | AC | Jira | Priority | Coverage | Cucumber Tag | Preconditions | Test Data | High-level Steps | Expected Result | Status | Note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TC-AA-037 | Entering Step 3 shows four document sections, two marked required | AC-AA-34 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-037 |
Step 2 is COMPLETED | — | 1. Open Upload vehicle documents | Banner reads "Select document to upload (*Required)"; four sections shown with "Upload file": Additional pictures and documents * (required), Damage preview page * (required), Details damage 1 (optional), Other (optional) | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 17.03.24.png |
| TC-AA-038 | "Upload file" opens the document camera with corner-guide instructions | AC-AA-35 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-038 |
User is on the Upload vehicle documents screen | Section: Damage preview page | 1. Tap Upload file for Damage preview page | Camera opens with prompt "Please capture the document with all four corners visible" | ⬜ Not Run | |
| TC-AA-039 | Multi-page capture shows a page counter | AC-AA-36 | RC-110 | 🟡 Medium | 🔵 Pending | @TC-AA-039 |
Document camera is open for Additional pictures and documents | 4-page document | 1. Capture page 1 2. Capture pages 2-4 in sequence |
Page counter (e.g. "1/4" → "4/4") tracks captured pages | ⬜ Not Run | |
| TC-AA-040 | Captured pages appear as removable thumbnails | AC-AA-37 | RC-110 | 🟡 Medium | 🔵 Pending | @TC-AA-040 |
≥1 page captured for Additional pictures and documents | — | 1. Return to Upload vehicle documents | Captured pages shown as thumbnails under Additional pictures and documents, each with an "x" | ⬜ Not Run | |
| TC-AA-041 | User can remove an uploaded page | AC-AA-38 | RC-110 | 🟡 Medium | 🔵 Pending | @TC-AA-041 |
Additional pictures and documents has ≥1 captured page thumbnail | — | 1. Tap "x" on a thumbnail | The page is removed from that section | ⬜ Not Run | |
| TC-AA-042 | "Fortfahren" completes Step 3 once both required documents are uploaded | AC-AA-39 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-042 |
Both required documents uploaded: Additional pictures and documents, Damage preview page | — | 1. Tap Fortfahren | Returns to Overview; "Capture vehicle documents" shows COMPLETED | ⬜ Not Run |
10. Step 4 — Vehicle Part Details (AI Review & Manual Damage Entry)¶
| TC ID | Test Scenario | AC | Jira | Priority | Coverage | Cucumber Tag | Preconditions | Test Data | High-level Steps | Expected Result | Status | Note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TC-AA-043 | Entering Step 4 shows the AI-results intro screen with an auto-proceed countdown | AC-AA-40 | RC-110 | 🟡 Medium | 🔵 Pending | @TC-AA-043 |
Step 3 is COMPLETED | — | 1. Open Vehicle part details | Intro screen shows "Review our AI Results..." with a "Proceed in N seconds" countdown | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 11.16.15.png |
| TC-AA-044 | The countdown (or manual Proceed) opens the Vehicle part details editor | AC-AA-41 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-044 |
AI-results intro screen shown, countdown running | — | 1. Wait for the countdown to reach 0 (or tap Proceed if enabled) | Vehicle part details editor opens | ⬜ Not Run | |
| TC-AA-045 | Vehicle part details shows a tappable front-side car diagram | AC-AA-42 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-045 |
User is on the Vehicle part details editor, Part detail tab | — | 1. View the diagram | FRONT SIDE diagram shows labeled tappable parts: Hood, Windshield, R./L. Headlight, R./L. Bumper, Grill | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 11.16.15.png |
| TC-AA-046 | First-time guidance walks the user through adding damage | AC-AA-43 | RC-110 | ⚪ Low | 🔵 Pending | @TC-AA-046 |
User opens Vehicle part details for the first time | — | 1. View the screen on first entry | Tooltips appear in sequence: "Please tap on the parts to add damage" → "Please tap on the button to add damage" | ⬜ Not Run | |
| TC-AA-047 | Tapping a car part opens the damage-entry panel for that part | AC-AA-44 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-047 |
User is on the Vehicle part details editor | Part: L.Headlight | 1. Tap L.Headlight on the diagram 2. Tap Add damaged part+ |
Damage-entry panel opens for L.Headlight | ⬜ Not Run | |
| TC-AA-048 | Damage-entry panel supports selecting more than one damage type | AC-AA-45 | RC-110 | 🟡 Medium | 🔵 Pending | @TC-AA-048 |
Damage-entry panel open for a part | Damage types: Scratch, Dent | 1. Select Scratch 2. Also select Dent |
Both damage types applied to the part (later shown as "Scratch, Dent") | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 11.16.27.png |
| TC-AA-049 | User sets the damaged car part, side 1, and side 2 | AC-AA-46 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-049 |
Damage-entry panel is open | Part: Backlight; Side1: Rear; Side2: Left | 1. Select Damaged car part = Backlight 2. Select Damaged side 1 = Rear 3. Select Damaged side 2 = Left |
Selections are set on the entry form | ⬜ Not Run | |
| TC-AA-050 | "Add" saves the damaged-part entry to the list | AC-AA-47 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-050 |
Damage-entry panel filled: Scratch, Backlight, Rear, Left | — | 1. Tap Add | Entry appears in "List of damaged parts" as "Rear left backlight — Scratch" with an edit (pencil) icon | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 11.16.27.png |
| TC-AA-051 | User can switch between FRONT SIDE and REAR SIDE diagrams | AC-AA-48 | RC-110 | 🟡 Medium | 🔵 Pending | @TC-AA-051 |
User is on the Vehicle part details editor | — | 1. Tap the right arrow to go to REAR SIDE 2. Tap the left arrow to return to FRONT SIDE |
The diagram switches sides and shows the relevant parts each time | ⬜ Not Run | |
| TC-AA-052 | "Select All" and the trash icon bulk-remove damaged-part entries | AC-AA-49 | RC-110 | 🟡 Medium | 🔵 Pending | @TC-AA-052 |
2 damaged parts listed (Rear right backlight, Rear left backlight) | — | 1. Tap Select All (2 Selected) 2. Tap the trash icon |
Both entries removed from "List of damaged parts" | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 11.16.27.png |
| TC-AA-053 | "Done" completes Step 4 and marks all four steps COMPLETED | AC-AA-50 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-053 |
≥1 damaged part added | — | 1. Tap Done | Returns to Overview; "Vehicle part details" and all 4 steps show COMPLETED | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 11.16.27.png |
11. Final Step — Completion, Next Actions & Send Report¶
| TC ID | Test Scenario | AC | Jira | Priority | Coverage | Cucumber Tag | Preconditions | Test Data | High-level Steps | Expected Result | Status | Note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TC-AA-054 | All steps COMPLETED shows the "Thank you" summary | AC-AA-51 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-054 |
All 4 steps (Accident details, Accident Photo and Video, Capture vehicle documents, Vehicle part details) COMPLETED | — | 1. View the Overview | "Thank you for completing all the steps" shown; all 4 items marked COMPLETED | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 11.16.27.png |
| TC-AA-055 | The summary lists four next-action options | AC-AA-52 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-055 |
User is on the "Thank you" summary screen | — | 1. View "Please choose what to do next with your damaged vehicle" | 4 options listed: Request for repair cost, Check repair shops near me, Find me a lawyer, Find me an expert | ⬜ Not Run | |
| TC-AA-056 | Requesting an action shows its status as "Appointment requested" | AC-AA-53 | RC-110 | 🟡 Medium | 🔵 Pending | @TC-AA-056 |
User is on the "Thank you" summary screen | Option: Check repair shops near me | 1. Select Check repair shops near me and complete its request flow | Option shows "Appointment requested" with provider details (e.g. John Doe / Riparo Workshops) | ⬜ Not Run | Cross-check with the per-expert selection flow decisions (see expert-call-appointment-decisions memory, RC-112) |
| TC-AA-057 | User can add one or more recipient email addresses to "Send report" | AC-AA-54 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-057 |
User is on the "Send report" section | Email: christina@gmail.com |
1. Type the email 2. Tap Add |
Email appears as a chip in the recipient list | ⬜ Not Run | |
| TC-AA-058 | User can remove an added email address before sending | AC-AA-55 | RC-110 | 🟡 Medium | 🔵 Pending | @TC-AA-058 |
≥1 email chip added | Email chip: johndoe@gmail.com |
1. Tap "x" on the email chip | The email is removed from the recipient list | ⬜ Not Run | |
| TC-AA-059 | "Send report" is disabled until the Privacy Policy is agreed | AC-AA-56 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-059 |
≥1 recipient email added; Privacy Policy checkbox unchecked | — | 1. Attempt to tap Send report | Send report remains disabled; no report is sent | ⬜ Not Run | Negative |
| TC-AA-060 | Sending the report generates a PDF and emails it to the added addresses | AC-AA-57 | RC-110 | 🔴 Critical | 🔵 Pending | @TC-AA-060 |
≥1 recipient email added; Privacy Policy checkbox checked | Emails: christina@gmail.com, johndoe@gmail.com |
1. Check "I have read and agree to the Privacy Policy" 2. Tap Send report |
A PDF report is generated and sent to each added email address | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 11.16.27.png |
12. Business Rules & Regression (Steps 2–4 & Final)¶
| TC ID | Test Scenario | AC | Jira | Priority | Coverage | Cucumber Tag | Preconditions | Test Data | High-level Steps | Expected Result | Status | Note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TC-AA-061 | Step 2 required-vs-optional gating is enforced end-to-end | BR-AA-05 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-061 |
Step 2 checklist visible | Combinations: (a) neither required item done, (b) only photos done, (c) only video done, (d) both done | 1. For each combination (a)-(d), attempt to leave Step 2 / return to Overview | Step 2 shows COMPLETED only for combination (d); IN PROGRESS otherwise | ⬜ Not Run | Equivalence classes on required items |
| TC-AA-062 | Multi-select damage type persists correctly on a saved entry | BR-AA-06 | RC-110 | 🟡 Medium | 🔵 Pending | @TC-AA-062 |
Damage-entry panel open for Rear right backlight | Damage types: Scratch + Dent | 1. Select both Scratch and Dent 2. Tap Add 3. Reopen the entry via the edit (pencil) icon |
Both damage types are shown/preserved on the saved entry | ⬜ Not Run | |
| TC-AA-063 | "Send report" gating holds regardless of email count | BR-AA-07 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-063 |
Privacy Policy checkbox unchecked | Emails: 0, 1, and 3 recipients added, in turn | 1. With 0, then 1, then 3 emails added — each time attempt Send report without checking the Privacy Policy | Send report stays disabled in all three cases | ⬜ Not Run | Boundary: recipient count does not override the consent gate |
| TC-AA-064 | "Thank you" summary only appears once all four steps are COMPLETED | BR-AA-08 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-064 |
3 of 4 steps COMPLETED, 1 step still IN PROGRESS/NOT STARTED | — | 1. View the Overview with only 3 steps COMPLETED 2. Complete the 4th step 3. View the Overview again |
"Thank you" summary is absent while any step is incomplete; appears only once all 4 are COMPLETED | ⬜ Not Run | Regression guard for the completion gate |
| TC-AA-065 | Required document sections are visually marked with a red asterisk | BR-AA-09 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-065 |
User is on the Upload vehicle documents screen | — | 1. Inspect each of the four section labels | "Additional pictures and documents" and "Damage preview page" show a red asterisk (*); "Details damage 1" and "Other" do not | ⬜ Not Run | UI ref: 01_Features/accident/wa_accident_assistant/screens/Screenshot 2026-08-06 at 17.03.24.png |
| TC-AA-066 | "Fortfahren" stays disabled while a required document is missing | AC-AA-58 | RC-110 | 🟠 High | 🔵 Pending | @TC-AA-066 |
Upload vehicle documents screen; only "Damage preview page" uploaded, "Additional pictures and documents" not uploaded | — | 1. Observe the Fortfahren button state. 2. Attempt to tap it. | Fortfahren is disabled/greyed out; tapping it has no effect and the user is not navigated to the Overview | ⬜ Not Run | |
| TC-AA-067 | Step 3 completes without the two optional documents | AC-AA-59 | RC-110 | 🟡 Medium | 🔵 Pending | @TC-AA-067 |
Both required documents uploaded; "Details damage 1" and "Other" left empty | — | 1. Tap Fortfahren. | Step 3 completes successfully; user returns to Overview with "Capture vehicle documents" COMPLETED, despite the two optional sections being empty | ⬜ Not Run |
Gherkin Mapping (Automated TCs only)¶
No TCs are automated yet — all 65 are 🔵 Pending. Add
.featurescenarios here as automation is implemented.