QA - ETC Platform API for Host Registration Validation

[rstens]

🧭 Exploratory Testing Charter: Host Registration Validation via API Integration

🎯 Purpose

Explore the API integration to:

1. Validate host registration details (registration number, address) with the external registry.
2. Verify API responses for address mismatches, status updates, and bulk operations.
3. Handle errors and ensure accurate messaging when the registry is unavailable.

---

🔍 Key Areas to Explore

1️⃣ Real-Time Registration Validation via API

• Trigger: Registration details are sent to the registry API during creation, publishing, or updates.
• Expected Outcome:
  • If details match, the system confirms the registration is valid.
  • If mismatched, the system returns an address mismatch error.

🌟 Scenarios:

• Scenario 1: Valid Registration Details
  Given the platform sends the registration number and address details to the registry,
  When the provided details match the registry’s records,
  Then the system returns a confirmation of the valid registration along with the status and registration number.

• Scenario 2: Address Mismatch
  Given the platform sends the registration number and address details to the registry,
  When the registry detects an address mismatch (e.g., unit number, street number, or postal code do not match),
  Then the system returns a failure message indicating the mismatch.

---

2️⃣ Handling API Errors and Unavailable Registry

• Trigger: API calls may fail or the external registry may become unavailable.
• Expected Outcome:
  • Users receive informative error messages if the API call fails or the registry is offline.

🌟 Scenarios:

• Scenario 3: API Call Fails or Registry Unavailable
  Given the platform attempts to validate a registration,
  When the registry is unavailable or the API call fails,
  Then the system displays an error message informing users that the validation could not be completed.

---

3️⃣ Bulk Daily API Verification

• Trigger: Platform sends a bulk request for multiple listings.
• Expected Outcome:
  • The registry processes multiple validation requests and returns results to a secure location for the platform to retrieve.

🌟 Scenarios:

• Scenario 4: Bulk Validation Request
  Given the platform sends a bulk request with multiple listings,
  When the registry processes the request,
  Then the platform receives a list of validation results at the designated secure location.

---

🔑 Business Rules Summary

1. API Request Structure:

   • Real-time validation requires:
     • Registration number
     • Unit number (if applicable)
     • Street number
     • Postal code
   • Bulk validation requests include multiple listings and corresponding registration details.

2. API Responses:

   • Code 404: Error (e.g., registry unavailable).
   • Code 1218: Address mismatch.
   • Status: ACTIVE, suspended, cancelled, or expired.

3. Error Handling:

   • If registration fails due to an unavailable registry or API failure, display error messages to users.

---

🛠️ Exploration Checklist

• [ ] Confirm that real-time API validation works with accurate status updates.
• [ ] Verify error handling when the API fails or the registry is offline.
• [ ] Test address mismatch responses and validate the error code (1218).
• [ ] Ensure bulk requests are processed correctly, with results stored in a secure location.
• [ ] Validate that informative messages are displayed to users during failures or mismatches.

---

🌐 Accessibility Scenarios

1. Keyboard Navigation

   • Given a keyboard user interacts with the API validation screens,
   • When they navigate through inputs and messages,
   • Then all elements should be accessible via Tab and Enter/Space keys.

2. Screen Reader Support

   • Given a screen reader user interacts with error messages,
   • When validation fails or an address mismatch occurs,
   • Then messages should be read aloud accurately.

3. High Contrast Mode

   • Given a user with low vision enables high contrast mode,
   • Then all API response messages and forms remain readable and functional.

---

🚀 Goal

Ensure registration validations are correctly processed with accurate API responses, robust error handling, and compliance with registry requirements.

[rstens]

Tester:

• [ ] Done

Session 1: Real-Time Registration Validation via API

• Focus: Validate that real-time registration checks return accurate results based on registry data.
• Scope: Confirm that the system correctly identifies valid registrations and provides clear error messages for mismatches.
• Goal: Ensure that the platform confirms valid registrations and detects address mismatches effectively.

Documentation

• Time Spent:
• What did you Test?
• Any Observations You Want to Share?
• Bug Report References:

---

[rstens]

Tester:

• [ ] Done

Session 2: Handling API Errors and Unavailable Registry

• Focus: Test the system’s response to registry unavailability or failed API calls.
• Scope: Ensure users receive appropriate error messages when validations cannot be processed due to registry issues or API failures.
• Goal: Provide seamless error handling to inform users of service disruptions.

Documentation

• Time Spent:
• What did you Test?
• Any Observations You Want to Share?
• Bug Report References:

---

[rstens]

Tester:

• [ ] Done

Session 3: Bulk Daily API Verification

• Focus: Validate that bulk requests are processed correctly with results stored securely.
• Scope: Test that the platform retrieves and stores results for multiple registration validations efficiently.
• Goal: Ensure smooth bulk operations with accurate status reporting for all listings.

Documentation

• Time Spent:
• What did you Test?
• Any Observations You Want to Share?
• Bug Report References:

---

[rstens]

Tester:

• [ ] Done

Session 4: API Response Validation and Error Codes

• Focus: Verify that the platform interprets API response codes accurately, such as address mismatches or registry unavailability.
• Scope: Ensure responses like Code 1218 (address mismatch) or Code 404 (unavailable registry) are handled properly.
• Goal: Ensure accurate status handling and user feedback for API responses.

Documentation

• Time Spent:
• What did you Test?
• Any Observations You Want to Share?
• Bug Report References:

---

[rstens]

Tester:

• [ ] Done

Session 5: Business Rules and API Request Structure Validation

• Focus: Ensure the platform follows the correct structure for API requests, including real-time and bulk validation.
• Scope: Validate that requests contain all necessary fields (registration number, unit number, street number, postal code).
• Goal: Confirm that all API requests align with the business rules and structure requirements.

Documentation

• Time Spent:
• What did you Test?
• Any Observations You Want to Share?
• Bug Report References:

---

[rstens]

Tester:

• [ ] Done

Session 6: Accessibility Testing

• Focus: Validate accessibility compliance for keyboard navigation, screen readers, and high contrast mode on the validation screens.
• Scope: Ensure error messages and forms are fully accessible for users with disabilities.
• Goal: Provide an inclusive and accessible experience during API validation processes.

Documentation

• Time Spent:
• What did you Test?
• Any Observations You Want to Share?
• Bug Report References:

---

[rstens]

Tester:

• [ ] Done

Session 7: Usability and Performance Testing

• Focus: Test the performance of real-time and bulk API operations under different conditions.
• Scope: Ensure that the system handles large data loads efficiently and provides quick responses to API requests.
• Goal: Confirm smooth usability and fast performance for all registration validation processes.

Documentation

• Time Spent:
• What did you Test?
• Any Observations You Want to Share?
• Bug Report References: