π§ Exploratory Testing Charter: Host Dashboard and Application Management
π― Purpose
Explore the host dashboard functionality to ensure hosts can effectively manage, view, and download submitted STRR applications. Validate accessibility, dynamic content behavior, and appropriate error handling.
π Key Areas to Explore
1οΈβ£ Dashboard View and Application Management
Trigger: Host accesses the dashboard via SBC Connect.
Expected Outcome:
Hosts can view all submitted STRR applications with details (e.g., address, status).
Hosts can create new applications from the dashboard.
Applications display as cards, with:
One application: wide card (single line).
Multiple applications: condensed cards (three per line).
If no applications exist, host is redirected to start a new application instead of viewing the dashboard.
π Scenarios:
Single Application Display: Given the host has one submitted application, Then it displays as a wide card with status and address.
Multiple Applications Display: Given the host has multiple applications, Then they are displayed in condensed format, grouped by status and ordered by location.
No Applications: Given the host has no applications, Then they are redirected to start a new application.
2οΈβ£ Viewing and Managing Individual Applications
Trigger: Host clicks an application card to view details.
Expected Outcome:
Opens in a new tab in read-only mode.
Displays latest data, rental property information, and status.
Hosts can download certificates if issued.
If certificates are unavailable, the download option is hidden.
π Scenarios:
View Application Details: Given the host clicks an application link, Then the system opens the details in a secure, read-only new tab.
Certificate Download: Given the application is approved, Then a "Download Certificate" button appears. When the host clicks "Download Certificate", Then it opens as a PDF in a new tab for download.
3οΈβ£ Registration Numbers and Provisional Approval
Trigger: Host views dashboard or application details.
Expected Outcome:
Display registration numbers for provisionally approved applications.
Provide tooltips explaining provisional approval.
Ensure error handling if registration numbers fail to generate.
π Scenarios:
Provisional Approval Display: Given an application is provisionally approved, Then the registration number appears on the dashboard and details page. When the host hovers over the registration number, Then a tooltip explains the provisional status.
4οΈβ£ Accessibility Testing
Ensure compliance with accessibility standards for keyboard navigation, screen readers, and low vision users.
π Scenarios:
Keyboard Navigation: Given a keyboard user navigates the dashboard, Then all interactive elements are accessible via Tab key and actionable with Enter/Space.
Screen Reader Support: Given a screen reader user accesses the dashboard, Then all content has appropriate labels and headings.
High Contrast Mode: Given a user enables high-contrast mode, Then the dashboard remains readable, with a consistent layout.
5οΈβ£ Global Usability & Performance Considerations
Confirm dashboard loads efficiently under different internet conditions.
Validate SBC Connect links in the footer and ensure they do not disrupt the user flow.
π Scenarios:
Internet Performance: Given a user accesses the dashboard with standard or low-speed internet, Then critical elements load first to maintain usability.
Mobile Responsiveness: Given a host accesses the dashboard on a mobile device, Then the layout adapts for easy navigation and interaction.
π Business Rules Summary
Dashboard Cards:
Use wide cards for one application and condensed cards for multiple applications.
Group applications by status, ordered by city/location.
Application Details:
Display applications in a new tab in read-only mode.
Provide error handling for unsuccessful tab loads.
Certificates:
Display download links only if certificates are available.
Certificates open in a PDF format for download in a new tab.
Registration Numbers:
Show registration numbers for provisional approvals with tooltips explaining status.
Ensure appropriate error handling if registration numbers fail to generate.
π οΈ Exploration Checklist
[ ] Verify dashboard layout (wide vs. condensed cards) based on the number of applications.
[ ] Confirm application details open in a new tab in read-only mode.
[ ] Validate certificate download functionality and PDF generation.
[ ] Test error handling for application and registration number failures.
[ ] Ensure tooltips appear correctly for provisional approval status.
[ ] Confirm accessibility compliance for keyboard, screen reader, and low-vision users.
[ ] Validate SBC Connect links do not disrupt the user flow.
[ ] Test mobile responsiveness and performance under various network conditions.
π Goal
Ensure a seamless, accessible, and efficient experience for hosts managing STRR applications, with clear options for viewing, downloading certificates, and tracking registration status.
Session 1: Dashboard View and Application Management
Focus: Validate the layout and behavior of the dashboard based on the number of applications.
Scope: Ensure single applications are displayed as wide cards and multiple applications as condensed cards. Confirm redirection to the application start page if no applications exist.
Goal: Ensure correct dashboard behavior and layout based on application count.
Documentation
Time Spent:
What did you Test?
Any Observations You Want to Share?
Bug Report References:
Session 2: Viewing and Managing Individual Applications
Focus: Test how hosts can view and interact with individual applications from the dashboard.
Scope: Validate that clicking an application card opens it in a new tab in read-only mode. Confirm that certificates are available for download only if issued.
Goal: Ensure smooth navigation to application details and proper handling of certificates.
Documentation
Time Spent:
What did you Test?
Any Observations You Want to Share?
Bug Report References:
Session 3: Registration Numbers and Provisional Approval
Focus: Test the display and functionality of registration numbers and tooltips.
Scope: Validate that registration numbers appear for provisionally approved applications. Ensure tooltips explain provisional approval status and error handling works for failed registrations.
Goal: Confirm accurate registration display and robust error handling.
Documentation
Time Spent:
What did you Test?
Any Observations You Want to Share?
Bug Report References:
Session 4: Accessibility Testing
Focus: Validate compliance with accessibility standards across the dashboard.
Scope: Test keyboard navigation, screen reader compatibility, and high-contrast mode to ensure all interactive elements are accessible and actionable.
Goal: Ensure the dashboard is accessible to all users, including those using assistive technologies.
Documentation
Time Spent:
What did you Test?
Any Observations You Want to Share?
Bug Report References:
Session 5: Global Usability & Performance Considerations
Focus: Validate dashboard performance and usability under different conditions.
Scope: Ensure fast loading under standard and low-speed internet. Confirm that SBC Connect links in the footer function correctly and do not disrupt the user flow. Validate mobile responsiveness.
Goal: Ensure reliable dashboard performance across devices and network conditions.
Documentation
Time Spent:
What did you Test?
Any Observations You Want to Share?
Bug Report References:
Session 6: Business Rules Validation
Focus: Validate the business rules governing the dashboard and application management.
Scope: Confirm that applications are grouped and displayed according to their status and location. Ensure certificates only appear when issued, and registration numbers follow proper error-handling processes.
Goal: Ensure all business rules are correctly implemented and reflected on the dashboard.
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 dashboard behavior.
Scope: Test scenarios such as network interruptions, failed certificate downloads, and invalid registration numbers. Validate behavior when a host attempts to access an unavailable application.
Goal: Identify and document potential issues or inconsistencies in dashboard behavior.
π§ Exploratory Testing Charter: Host Dashboard and Application Management
π― Purpose
Explore the host dashboard functionality to ensure hosts can effectively manage, view, and download submitted STRR applications. Validate accessibility, dynamic content behavior, and appropriate error handling.
π Key Areas to Explore
1οΈβ£ Dashboard View and Application Management
π Scenarios:
Single Application Display:
Given the host has one submitted application,
Then it displays as a wide card with status and address.
Multiple Applications Display:
Given the host has multiple applications,
Then they are displayed in condensed format, grouped by status and ordered by location.
No Applications:
Given the host has no applications,
Then they are redirected to start a new application.
2οΈβ£ Viewing and Managing Individual Applications
π Scenarios:
View Application Details:
Given the host clicks an application link,
Then the system opens the details in a secure, read-only new tab.
Certificate Download:
Given the application is approved,
Then a "Download Certificate" button appears.
When the host clicks "Download Certificate",
Then it opens as a PDF in a new tab for download.
3οΈβ£ Registration Numbers and Provisional Approval
π Scenarios:
Given an application is provisionally approved,
Then the registration number appears on the dashboard and details page.
When the host hovers over the registration number,
Then a tooltip explains the provisional status.
4οΈβ£ Accessibility Testing
Ensure compliance with accessibility standards for keyboard navigation, screen readers, and low vision users.
π Scenarios:
Keyboard Navigation:
Given a keyboard user navigates the dashboard,
Then all interactive elements are accessible via Tab key and actionable with Enter/Space.
Screen Reader Support:
Given a screen reader user accesses the dashboard,
Then all content has appropriate labels and headings.
High Contrast Mode:
Given a user enables high-contrast mode,
Then the dashboard remains readable, with a consistent layout.
5οΈβ£ Global Usability & Performance Considerations
π Scenarios:
Internet Performance:
Given a user accesses the dashboard with standard or low-speed internet,
Then critical elements load first to maintain usability.
Mobile Responsiveness:
Given a host accesses the dashboard on a mobile device,
Then the layout adapts for easy navigation and interaction.
π Business Rules Summary
Dashboard Cards:
Application Details:
Certificates:
Registration Numbers:
π οΈ Exploration Checklist
π Goal
Ensure a seamless, accessible, and efficient experience for hosts managing STRR applications, with clear options for viewing, downloading certificates, and tracking registration status.