QA - ETC SBC Connect Account Integration and Navigation

[rstens]

🧭 Exploratory Testing Charter: SBC Connect Account Integration and Navigation

🔍 Scope

This exploratory testing session will focus on validating the SBC Connect account selection, information access, and integration with the STRR application. It includes navigation back to STRR after accessing SBC Connect and ensuring seamless transitions between the systems.

---

🎯 Mission

Explore the SBC Connect integration within the STRR application to ensure:

1. Users can access SBC Connect information and notifications when authenticated.
2. Navigation between SBC Connect and STRR works as expected.
3. All elements are responsive and accessible across devices.

---

📋 Key Areas to Explore

1. SBC Connect Account Information and Notifications

• Verify that users authenticated via SBC Connect can access their account details.
• Ensure the notification center and account dropdown appear only when an SBC account is selected.

Test Ideas:

• Confirm notification center and account dropdown visibility after selecting an account.
• Test interactions with account settings and notifications through the dropdown.

---

2. Navigation Between SBC Connect and STRR

• Ensure users can seamlessly switch back to STRR from SBC Connect via the STRR card.
• Validate that returning to STRR redirects users to the appropriate section or page in their application.

Test Ideas:

• Access the SBC Connect platform and use the STRR card to return.
• Confirm the correct state of the application upon returning from SBC Connect.

---

3. Stepper Navigation and State Management

• Ensure the stepper highlights the current step and allows navigation between pages.
• Verify that account information and notifications remain accessible while users move through the form.

Test Ideas:

• Test navigation via stepper icons and confirm each page loads correctly.
• Ensure notifications remain available as users navigate through the application.

---

4. Logout Scenarios and Session Management

• Verify that users can log out from either SBC Connect or BC Services Card.
• Ensure logout prompts return users to the STRR login page.

Test Ideas:

• Log out from SBC Connect account and verify redirection to the login page.
• Test logging out from BC Services Card session and ensure proper logout handling.

---

5. Accessibility Checks

• Validate keyboard navigation through account dropdown and notifications.
• Ensure screen readers provide meaningful context for account-related elements.

Test Ideas:

• Navigate through the SBC Connect dropdown using only a keyboard.
• Use a screen reader to access account information and confirm correct element descriptions.

---

🔑 Business Rules to Validate

• SBC Connect Dropdown Visibility: Only visible if an SBC account is selected.
• Seamless Navigation: Users can return to STRR via the STRR card in SBC Connect.
• Logout Functionality: Users can log out from both SBC Connect and BC Services Card sessions.
• Responsive Layout: Elements such as the fee widget remain functional across devices.

---

🛠 Test Data

• Authenticated SBC Connect accounts with sample notifications.
• STRR application progress saved at different stages for navigation testing.

---

📌 Risks and Focus Areas

• Navigation Issues: Inconsistent state when switching between SBC Connect and STRR.
• Account Information Display: Incorrect or missing data in notifications or dropdowns.
• Logout Handling: Ensure proper session management across multiple systems.

---

📅 Test Session Details

• Duration: 90 minutes
• Resources: SBC Connect and STRR application in staging, keyboard, screen reader simulation tools
• Focus: Account integration, navigation, and accessibility compliance

---

🚀 Charter Outcomes

This session should yield:

1. Identification of any navigation or account integration issues.
2. Validation of notifications, dropdowns, and logout functionality.
3. Detection of accessibility gaps and recommendations for improvement.
4. Confirmation that SBC Connect and STRR integration meets user expectations and business requirements.

[rstens]

Session 1: SBC Connect Account Information and Notifications

• Focus: Validate the visibility and functionality of account information and notifications.
• Scope: Ensure authenticated users can access their SBC Connect account details and notifications through the account dropdown. Verify that these elements appear only when an SBC account is selected.
• Goal: Confirm correct display and interaction with the notification center and account dropdown.

Documentation

Time Spent:

What did you Test?

Any observations you want to share?

Bug Report References:

---

Session 2: Navigation Between SBC Connect and STRR

• Focus: Validate the seamless navigation between SBC Connect and the STRR application.
• Scope: Test navigation from SBC Connect to STRR using the STRR card. Ensure users are redirected to the appropriate page within STRR upon return.
• Goal: Confirm smooth transitions between systems without disrupting the user experience.

Documentation

Time Spent:

What did you Test?

Any observations you want to share?

Bug Report References:

---

Session 3: Stepper Navigation and State Management

• Focus: Test the behavior of the stepper and data persistence while navigating through the form.
• Scope: Ensure the stepper highlights the correct step and allows users to move between pages. Verify that notifications remain accessible as users navigate through the application.
• Goal: Ensure consistent state management and navigation within STRR.

Documentation

Time Spent:

What did you Test?

Any observations you want to share?

Bug Report References:

---

Session 4: Logout Scenarios and Session Management

• Focus: Validate the logout functionality from both SBC Connect and BC Services Card sessions.
• Scope: Test logout prompts to ensure users are returned to the STRR login page after logging out from SBC Connect or BC Services Card. Verify that session handling works correctly.
• Goal: Confirm that logout functionality is reliable and properly handled across systems.

Documentation

Time Spent:

What did you Test?

Any observations you want to share?

Bug Report References:

---

Session 5: Accessibility Checks

• Focus: Test the accessibility of the SBC Connect integration and account elements.
• Scope: Ensure that users can navigate through the SBC Connect dropdown and notifications using only a keyboard. Use a screen reader to confirm meaningful context for all account-related elements.
• Goal: Confirm compliance with accessibility standards for account elements and navigation.

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 governing the SBC Connect and STRR integration.
• Scope: Ensure that the SBC Connect dropdown is only visible when an account is selected. Verify seamless navigation back to STRR via the STRR card and confirm logout functionality for both systems.
• Goal: Ensure all business rules are correctly 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 related to account integration and navigation.
• Scope: Test scenarios such as switching accounts mid-session, accessing STRR after logging out from SBC Connect, and navigating between pages with unsaved changes. Ensure all systems handle these scenarios gracefully.
• Goal: Identify any edge cases that could disrupt the user experience or system functionality.

Documentation

Time Spent:

What did you Test?

Any observations you want to share?

Bug Report References: