Thinh Lam
67 lines
2.6 KiB
Markdown
67 lines
2.6 KiB
Markdown
# QA Test: Applicant Can Open Fresh Registration Forms
|
|
|
|
## Objective
|
|
Verify that an applicant user can start a **new** registration flow and open all required blank forms:
|
|
- Initiative report form
|
|
- Initiative application form
|
|
- Contribution confirmation form
|
|
|
|
## Scope
|
|
- Frontend route: `/dashboard`
|
|
- Fresh-mode trigger: `?fresh=1`
|
|
- Session reset behavior for applicant registration
|
|
|
|
## Preconditions
|
|
- App is running locally (`fe0` and required backend services).
|
|
- Test account exists with applicant access.
|
|
- Browser session is logged in as applicant.
|
|
- At least one old draft may exist (to confirm fresh reset ignores previous session state).
|
|
|
|
## Test Data
|
|
- Applicant account credentials
|
|
- Optional: existing draft case id from prior session
|
|
|
|
## Test Case 1: Direct Fresh Link Opens Blank Forms
|
|
1. Navigate to `/dashboard?fresh=1`.
|
|
2. Wait for dashboard to load completely.
|
|
3. Confirm the active tab is report form (first step).
|
|
4. Confirm report form fields are blank/default (not prefilled from previous draft).
|
|
5. Switch to application form tab.
|
|
6. Confirm application form is visible and blank/default.
|
|
7. Switch to contribution form tab.
|
|
8. Confirm contribution form is visible and blank/default.
|
|
|
|
Expected result:
|
|
- Dashboard opens in fresh mode.
|
|
- Applicant can open all three forms.
|
|
- No stale data from a previous draft appears.
|
|
|
|
## Test Case 2: "Create New" / Fresh Navigation from Applicant History
|
|
1. Open applicant history panel/page.
|
|
2. Click the action that starts a new application (fresh registration path).
|
|
3. Confirm browser lands on dashboard fresh flow.
|
|
4. Confirm report, application, and contribution forms are all accessible.
|
|
5. Confirm each form starts empty.
|
|
|
|
Expected result:
|
|
- Fresh navigation clears registration session state.
|
|
- Applicant can open all required forms for a brand-new submission.
|
|
|
|
## Test Case 3: Fresh Flow Clears Previous Draft Context
|
|
1. Start from a resumed draft (`/dashboard?caseId=<existing-id>`) and verify data is loaded.
|
|
2. Then navigate to `/dashboard?fresh=1`.
|
|
3. Confirm previously loaded draft values are no longer shown.
|
|
4. Confirm a new save operation creates/uses a new case id (not the previous one).
|
|
|
|
Expected result:
|
|
- Fresh mode always resets draft context and starts a new application flow.
|
|
|
|
## Regression Checks
|
|
- Applicant remains authenticated after entering fresh flow.
|
|
- No console errors while switching among tabs/forms.
|
|
- Page remains responsive after opening all forms.
|
|
|
|
## Pass/Fail Criteria
|
|
- **Pass**: Applicant can open all fresh forms and no stale draft data leaks into the new registration flow.
|
|
- **Fail**: Any required form fails to open, opens with stale data, or fresh navigation does not reset prior draft context.
|