QA - ETC SBC Connect Account Creation After Authentication

[rstens]

🧭 Exploratory Testing Charter: SBC Connect Account Creation After Authentication

🔍 Scope

This session focuses on testing the SBC Connect account creation process after the host has authenticated via Service BC. We aim to validate:

1. Seamless flow from authentication to account creation.
2. Data pre-population from the BC Services Card.
3. User experience and error handling during account creation.
4. Accessibility compliance and ease of use for diverse users.

---

🎯 Mission

Ensure the SBC Connect account creation process is intuitive, smooth, and error-free for hosts, enabling them to enter valid contact information and proceed with STR registration and payments.

---

📋 Key Areas to Explore

1. Pre-population of Fields from BC Services Card

• Validate that first name, middle name (if available), and last name are correctly pulled from BC Services Card.
• Ensure manual entry is required for the phone number and email address fields.

Test Ideas:

• Authenticate via Service BC and verify if name fields are auto-filled.
• Test with edge cases (e.g., long names, missing middle name) to confirm correct handling.

---

2. Account Creation Form Validation and Submission

• Ensure that phone numbers and email addresses are validated according to business rules.
• Check that optional phone extensions are limited to 1-5 numeric characters.

Test Ideas:

• Test with valid and invalid phone numbers to confirm error messages.
• Leave required fields blank and verify error handling.
• Try entering a valid email address with edge cases (e.g., long domain names).

---

3. User Flow and Account Confirmation

• Validate the flow from authentication to account creation and confirmation.
• Ensure users receive appropriate feedback when their account is created.

Test Ideas:

• Complete the process and confirm the account creation confirmation message.
• Attempt to create a new account even if an existing account exists to validate that it’s allowed.

---

4. Accessibility Validation

• Ensure all form fields and elements are accessible via screen readers and keyboard.

Test Ideas:

• Navigate the form using only a keyboard to verify accessibility.
• Use a screen reader to confirm proper labeling of fields and instructions.

---

🔑 Business Rules to Validate

• First name, middle name (if available), and last name are pulled from the BC Services Card.
• Phone number is required and must be valid.
• Email address is required and must follow the format: username + "@" + domain.
• Phone extension is optional, limited to 1-5 digits.
• The created account defaults to a basic SBC account.

---

🛠 Test Data

• BC Services Card credentials for testing successful authentication.
• Test cases with various phone numbers, email formats, and optional fields.

---

📌 Risks and Focus Areas

• Incorrect data pre-population from the BC Services Card.
• Validation issues for phone numbers and emails leading to submission failures.
• Accessibility gaps in form navigation and error messaging.

---

📅 Test Session Details

• Duration: 90 minutes
• Resources: Keyboard, screen reader tools, BC Services Card test environment
• Focus: Data validation, user flow, and accessibility compliance

---

🚀 Charter Outcomes

This session should deliver:

1. Identification of user flow or data pre-population issues.
2. Validation of error handling and business rule compliance.
3. Confirmation that the account creation process is seamless and intuitive.
4. Identification of accessibility gaps with actionable recommendations.

[rstens]

Tester:

• [ ] Done

Session 1: Pre-population of Fields from BC Services Card

• Focus: Validate data pre-population from the BC Services Card during account creation.
• Scope: Verify that first name, middle name (if available), and last name fields are correctly auto-filled. Ensure users manually enter the phone number and email address.
• Goal: Confirm that data pre-population works correctly and handles edge cases (e.g., long names or missing middle names).

Documentation

Time Spent:

What did you Test?

Any observations you want to share?

Bug Report References:

---

[rstens]

Tester:

• [ ] Done

Session 2: Account Creation Form Validation and Submission

• Focus: Validate form field validation and error handling.
• Scope: Ensure phone numbers, email addresses, and phone extensions follow business rules. Verify error handling when required fields are left blank or invalid data is entered.
• Goal: Confirm smooth form submission with appropriate error messages for invalid inputs.

Documentation

Time Spent:

What did you Test?

Any observations you want to share?

Bug Report References:

---

[rstens]

Tester:

• [ ] Done

Session 3: User Flow and Account Confirmation

• Focus: Validate the entire user flow from authentication to account creation and confirmation.
• Scope: Confirm users receive feedback upon account creation. Test scenarios where users attempt to create new accounts, even if an account already exists.
• Goal: Ensure a seamless user flow with appropriate confirmation messages.

Documentation

Time Spent:

What did you Test?

Any observations you want to share?

Bug Report References:

---

[rstens]

Tester:

• [ ] Done

Session 4: Accessibility Validation

• Focus: Test the accessibility of the account creation form.
• Scope: Ensure all form fields and elements are accessible through keyboard navigation and screen readers. Verify proper field labeling and instructions.
• Goal: Confirm compliance with accessibility standards.

Documentation

Time Spent:

What did you Test?

Any observations you want to share?

Bug Report References:

---

[rstens]

Tester:

• [ ] Done

Session 5: Business Rules Validation

• Focus: Validate business rules governing the account creation process.
• Scope: Verify that names are pulled from the BC Services Card, phone numbers are required, and email addresses follow the correct format. Ensure phone extensions are optional and limited to 1-5 digits.
• Goal: Ensure all business rules are correctly implemented.

Documentation

Time Spent:

What did you Test?

Any observations you want to share?

Bug Report References:

---

[rstens]

Tester:

• [ ] Done

Session 6: Key Scenarios and Edge Cases

• Focus: Explore edge cases and unusual scenarios for account creation.
• Scope: Test scenarios such as creating accounts with existing SBC accounts, entering long email addresses, or using unusual phone formats. Confirm the form handles these scenarios gracefully.
• Goal: Identify any potential issues or edge cases in the account creation process.

Documentation

Time Spent:

What did you Test?

Any observations you want to share?

Bug Report References: