π§ Exploratory Testing Charter: Application Confirmation After Payment
π― Purpose
Explore the confirmation flow after successful payment to ensure that hosts receive a clear submission confirmation and appropriate next steps. Validate accessibility, navigation, and performance of the confirmation page.
π Key Areas to Explore
1οΈβ£ Application Submission Confirmation
Trigger: Successful payment completion.
Expected Outcome:
Display confirmation that the STRR application has been submitted.
Provide clear next steps, including:
Option to start a new application.
Access the SBC Connect profile.
Navigate to the Host Dashboard.
π Scenarios:
Confirmation Display: Given a host completes payment, Then the system displays the "Application Received Confirmation" page with next-step options.
Navigation Options: Given the host is on the confirmation page, Then the host can:
Start a new application.
Navigate to their SBC Connect profile.
Go to the Host Dashboard.
2οΈβ£ Accessibility Testing
Ensure compliance with accessibility standards for keyboard navigation, screen readers, and low vision users.
π Scenarios:
Keyboard Navigation: Given a keyboard user navigates using the Tab key, Then all interactive elements are accessible and actionable using Enter/Space.
Screen Reader Support: Given a screen reader user navigates the confirmation page, Then all elements have appropriate alt texts and structured headings.
High Contrast Mode: Given a user enables high-contrast mode, Then content remains readable, and the layout stays consistent.
3οΈβ£ Global Usability & Navigation Considerations
Validate external SBC Connect links in the footer or elsewhere, ensuring they do not interrupt the current flow.
Confirm the mobile responsiveness of the confirmation page.
π Scenarios:
SBC Connect Links: Given the host interacts with SBC Connect links in the footer, Then confirm they are functional and do not unintentionally disrupt the STRR application flow.
Mobile Compatibility: Given a host accesses the confirmation page on a mobile device, Then the layout should be responsive, and all elements easily accessible.
4οΈβ£ Performance Testing
Ensure pages load efficiently under various network conditions.
π Scenarios:
Standard Internet Connection: Given a host navigates to the confirmation page with a standard connection, Then the page should load within 2 seconds.
Low-Speed Internet: Given a user accesses the confirmation page with a low-speed connection, Then essential content should load first to ensure usability.
π Business Rules Summary
Confirmation Page Actions:
Show message confirming submission of the rental application.
Provide options to:
Start a new application.
Access SBC Connect profile.
Go to the Host Dashboard.
SBC Connect Links:
Ensure these links do not disrupt the STRR application process.
π οΈ Exploration Checklist
[ ] Verify successful display of the application confirmation page after payment.
[ ] Ensure navigation options (new application, dashboard, SBC Connect) work as expected.
[ ] Confirm accessibility compliance for keyboard, screen readers, and low-vision users.
[ ] Validate the correct behavior of SBC Connect links across the page and footer.
[ ] Test page responsiveness on mobile devices.
[ ] Ensure fast page loading under standard and low-speed internet conditions.
π Goal
Ensure a smooth, intuitive, and accessible post-payment confirmation experience, with clear navigation and next steps for the host.
Focus: Validate the confirmation page display and next-step options after successful payment.
Scope: Ensure the system displays a confirmation message upon submission with options to start a new application, access SBC Connect, or navigate to the Host Dashboard.
Goal: Confirm that the confirmation page is clear, informative, and provides correct navigation options.
Documentation
Time Spent:
What did you Test?
Any Observations You Want to Share?
Bug Report References:
Session 2: Accessibility Testing
Focus: Ensure accessibility compliance for the confirmation page.
Scope: Validate keyboard navigation, screen reader compatibility, and support for high-contrast mode. Confirm that all elements are accessible and actionable using standard accessibility tools.
Goal: Ensure the confirmation page meets WCAG 2.1 standards, providing a seamless experience for all users.
Documentation
Time Spent:
What did you Test?
Any Observations You Want to Share?
Bug Report References:
Session 3: Global Usability & Navigation Considerations
Focus: Validate the usability and navigation of the confirmation page.
Scope: Ensure that SBC Connect links in the footer or elsewhere function correctly without disrupting the application flow. Confirm the page is mobile-responsive.
Goal: Ensure smooth navigation, both on desktop and mobile, with uninterrupted access to SBC Connect links.
Documentation
Time Spent:
What did you Test?
Any Observations You Want to Share?
Bug Report References:
Session 4: Performance Testing
Focus: Test the performance of the confirmation page under different network conditions.
Scope: Validate that the page loads within 2 seconds on standard connections. Ensure that critical content loads first under low-speed internet conditions to maintain usability.
Goal: Confirm fast and reliable page performance across all environments.
Documentation
Time Spent:
What did you Test?
Any Observations You Want to Share?
Bug Report References:
Session 5: Business Rules Validation
Focus: Validate the confirmation page actions and business rules.
Scope: Ensure the confirmation page shows the correct submission message and provides options to start a new application, access SBC Connect, or go to the Host Dashboard. Verify that SBC Connect links function as intended without disrupting the STRR process.
Goal: Confirm all business rules are correctly implemented and reflected in the confirmation page actions.
Documentation
Time Spent:
What did you Test?
Any Observations You Want to Share?
Bug Report References:
Session 6: Key Scenarios and Edge Cases
Focus: Explore key scenarios and edge cases related to the confirmation flow.
Scope: Test scenarios such as accessing SBC Connect links mid-navigation, using the confirmation page on different devices, and testing navigation with interrupted sessions. Ensure consistent behavior across all scenarios.
Goal: Identify potential issues or edge cases that could disrupt the user experience.
π§ Exploratory Testing Charter: Application Confirmation After Payment
π― Purpose
Explore the confirmation flow after successful payment to ensure that hosts receive a clear submission confirmation and appropriate next steps. Validate accessibility, navigation, and performance of the confirmation page.
π Key Areas to Explore
1οΈβ£ Application Submission Confirmation
π Scenarios:
Confirmation Display:
Given a host completes payment,
Then the system displays the "Application Received Confirmation" page with next-step options.
Navigation Options:
Given the host is on the confirmation page,
Then the host can:
2οΈβ£ Accessibility Testing
Ensure compliance with accessibility standards for keyboard navigation, screen readers, and low vision users.
π Scenarios:
Keyboard Navigation:
Given a keyboard user navigates using the Tab key,
Then all interactive elements are accessible and actionable using Enter/Space.
Screen Reader Support:
Given a screen reader user navigates the confirmation page,
Then all elements have appropriate alt texts and structured headings.
High Contrast Mode:
Given a user enables high-contrast mode,
Then content remains readable, and the layout stays consistent.
3οΈβ£ Global Usability & Navigation Considerations
π Scenarios:
SBC Connect Links:
Given the host interacts with SBC Connect links in the footer,
Then confirm they are functional and do not unintentionally disrupt the STRR application flow.
Mobile Compatibility:
Given a host accesses the confirmation page on a mobile device,
Then the layout should be responsive, and all elements easily accessible.
4οΈβ£ Performance Testing
π Scenarios:
Standard Internet Connection:
Given a host navigates to the confirmation page with a standard connection,
Then the page should load within 2 seconds.
Low-Speed Internet:
Given a user accesses the confirmation page with a low-speed connection,
Then essential content should load first to ensure usability.
π Business Rules Summary
Confirmation Page Actions:
SBC Connect Links:
π οΈ Exploration Checklist
π Goal
Ensure a smooth, intuitive, and accessible post-payment confirmation experience, with clear navigation and next steps for the host.