QA - ETC Review and Submit Page

[rstens]

🧭 Exploratory Testing Charter: Review and Submit Page

🔍 Scope

This exploratory testing session focuses on validating the Review and Submit Page of the STRR application. The session will cover key workflows such as reviewing entered data, navigating back to edit forms, validating required terms acceptance, and ensuring proper error handling on submission.

---

🎯 Mission

Explore the Review and Submit Page to ensure:

1. Hosts can easily review their entire application before submission.
2. The navigation via steppers and back/next buttons preserves all data.
3. Critical validations such as acceptance of terms and certifications function properly.
4. Usability, accessibility, and error-handling mechanisms enhance user satisfaction.

---

📋 Key Areas to Explore

1. Review and Data Display

• Verify that all sections (Contact Info, Property Details, PR Requirements) are displayed in read-only mode.
• Ensure the uploaded documents from PR Requirements are visible but not editable.
• Check that completed sections show checkmarks in the stepper.

Test Ideas:

• Review the entire application and confirm the presence of all sections.
• Upload documents and validate they appear in the read-only list.
• Navigate between sections and ensure the stepper state reflects progress.

---

2. Navigation and Editing via Steppers and Buttons

• Ensure users can navigate back to any section for editing via the stepper or back buttons.
• Verify that any changes made in forms are saved upon returning to the review page.

Test Ideas:

• Click a stepper for Property Details to make changes, then return to the review page.
• Test if back/next buttons preserve form state and lead to the appropriate pages.
• Validate state persistence by making changes in multiple sections.

---

3. Terms and Conditions Acceptance

• Ensure the checkbox for accepting terms is unchecked by default.
• Verify that users cannot submit the application without checking the acceptance box.
• Validate the acceptance selection is stored in the system as agreedToSubmit = true.

Test Ideas:

• Attempt to submit the application without checking the terms box; verify error messages.
• Open DevTools to confirm that the agreedToSubmit field is recorded as true after submission.
• Reload the review page and confirm the checkbox state.

---

4. Error Handling and Submission Workflow

• Ensure that any missed requirements or errors are indicated with a red X on the stepper.
• Verify that errors are clearly highlighted with instructions for correction.
• Check that the application is marked as "Payment Due" upon submission.

Test Ideas:

• Submit the form with missing data and verify the stepper shows red Xs on relevant sections.
• Make corrections and confirm that the red X changes to a green checkmark.
• Ensure account creation and application status updates correctly after submission.

---

5. Accessibility and Usability Checks

• Validate full keyboard navigation and interaction (Tab, Enter, Space keys).
• Ensure proper alt text for images and logical screen reader content structure.
• Check high contrast mode and text resizing support.

Test Ideas:

• Navigate the entire form using only a keyboard.
• Use a screen reader to test form navigation and field descriptions.
• Enable high contrast mode and validate content readability.

---

🔑 Business Rules to Validate

• Stepper State: Completed sections show checkmarks; review page highlights the active step.
• Data Persistence: All changes made via steppers or buttons are saved and reflected on review.
• Read-Only Mode: Review page content is non-editable; users can only make changes by navigating back.
• Terms Acceptance: The application cannot be submitted without accepting the terms.
• Error Handling: Fields with errors are marked with red Xs, and error messages provide correction guidance.

---

🛠 Test Data

• Contact Info: Sample primary and secondary contact information.
• Property Details: Rental address with nickname, postal code.
• PR Requirements: Various exemption cases and uploaded documents (PDF, JPG).

---

📌 Risks and Focus Areas

• Navigation errors: Risk of incomplete data being lost if the state isn't preserved.
• Inadequate error messaging: Ensure errors are clear and actionable.
• Accessibility compliance: Confirm the page is accessible for all user groups.

---

📅 Test Session Details

• Duration: 90 minutes
• Resources: STRR form UI in staging, keyboard, screen reader simulation tools
• Focus: Review and Submit workflow, error handling, and accessibility compliance

---

🚀 Charter Outcomes

This session should yield:

1. A list of usability or navigation issues.
2. Validation of all business rules, including error handling and terms acceptance.
3. Identification of any accessibility gaps.
4. Recommendations to improve the user experience before final release.

[rstens]

Session 1: Review and Data Display

• Focus: Validate the display of all sections in read-only mode.
• Scope: Ensure all sections (Contact Info, Property Details, PR Requirements) are displayed correctly, with uploaded documents visible but not editable. Check that completed sections show checkmarks in the stepper.
• Goal: Confirm that users can review their entire application without editing and that the stepper reflects progress accurately.

Documentation

Time Spent:

What did you Test?

Any observations you want to share?

Bug Report References:

---

Session 2: Navigation and Editing via Steppers and Buttons

• Focus: Validate the navigation and editing functionality.
• Scope: Ensure users can navigate back to any section for editing via the stepper or back buttons, and that changes are saved upon returning to the review page.
• Goal: Confirm that changes made in forms are preserved and reflected in the review section, and that stepper navigation works as expected.

Documentation

Time Spent:

What did you Test?

Any observations you want to share?

Bug Report References:

---

Session 3: Terms and Conditions Acceptance

• Focus: Validate the terms and conditions acceptance workflow.
• Scope: Ensure the checkbox for accepting terms is unchecked by default and that users cannot submit the application without checking it. Verify that the agreedToSubmit field is set to true upon submission.
• Goal: Confirm that the application cannot be submitted without terms acceptance and that this selection is stored properly.

Documentation

Time Spent:

What did you Test?

Any observations you want to share?

Bug Report References:

---

Session 4: Error Handling and Submission Workflow

• Focus: Test error handling and the submission process.
• Scope: Ensure that missed requirements or errors are highlighted with a red X on the stepper, and that errors are clearly displayed with instructions for correction. Verify that the application is marked as "Payment Due" upon successful submission.
• Goal: Confirm that error handling and status updates function correctly, providing clear feedback to the user.

Documentation

Time Spent:

What did you Test?

Any observations you want to share?

Bug Report References:

---

Session 5: Accessibility and Usability Checks

• Focus: Validate accessibility and usability of the Review and Submit page.
• Scope: Ensure full keyboard navigation (Tab, Enter, Space keys) and logical screen reader structure. Check alt text for images and support for high contrast mode and text resizing.
• Goal: Confirm the page meets accessibility standards and provides a seamless experience for all user types.

Documentation

Time Spent:

What did you Test?

Any observations you want to share?

Bug Report References:

---

Session 6: Business Rules Validation

• Focus: Validate business rules on the Review and Submit page.
• Scope: Ensure completed sections display checkmarks in the stepper, and the review page is non-editable. Confirm data persistence, terms acceptance, and error handling align with business rules.
• Goal: Verify all business rules are properly implemented and function as expected.

Documentation

Time Spent:

What did you Test?

Any observations you want to share?

Bug Report References:

---

Session 7: Key Scenarios and Edge Cases

• Focus: Explore key scenarios and edge cases for the Review and Submit workflow.
• Scope: Test scenarios such as submitting without accepting terms, navigating away with unsaved changes, and attempting to submit with missing data. Ensure errors are correctly handled, and form states are preserved.
• Goal: Identify any edge cases that could lead to issues with the submission process or data validation.

Documentation

Time Spent:

What did you Test?

Any observations you want to share?

Bug Report References: