QA -ETC Automatic Application Flagging and Full Review Logic

[rstens]

🧭 Exploratory Testing Charter: Automatic Application Flagging and Full Review Logic

🎯 Purpose

Explore the logic for flagging applications for Full Review based on property ownership, exemption status, and local regulations. Validate that applications are correctly flagged to bypass automatic approvals and that appropriate statuses are applied.

---

🔍 Key Areas to Explore

1️⃣ Flagging for Full Review Based on Ownership and Exemptions

• Trigger: Host selects "Rent" under ownership or specific exemptions during the application process.
• Expected Outcome:
  • If Rent or Exempt Accommodation Provider is selected, the system flags the application for Full Review.
  • If the host selects Strata Hotel or Farm Land for PR exemption, the application is sent for Full Review.

🌟 Scenarios:

• Rent as Ownership:
  Given the host selects "Rent" under ownership,
  When the payment is successfully processed,
  Then the system flags the application for Full Review.

• Exempt Accommodation Provider:
  Given the host selects "Other Exempt Accommodation Service Provider,"
  Then the system flags the application for Full Review and displays the status accordingly.

• Strata Hotel or Farm Land PR Exemption:
  Given the host selects "Strata Hotel" or "Farm Land" as a PR exemption reason,
  Then the system flags the application for Full Examination.

---

2️⃣ PR Exemption and Automatic Approval

• Trigger: The system determines whether a property qualifies as PR Exempt.
• Expected Outcome:
  • If PR Exempt, status changes to Auto Approved.
  • If not PR Exempt, status remains Applied.
  • If address is not found or API fails, status defaults to Full Review.

🌟 Scenarios:

• PR Exempt Area:
  Given the system flags the property as PR Exempt,
  Then the application status changes to Auto Approved.

• API Failure or Address Not Found:
  Given the API fails or the address is not found,
  Then the application status defaults to Full Review with appropriate flags.

---

3️⃣ Business License and STR Prohibition Checks

• Trigger: The system checks if a business license is required or STR operation is prohibited in the area.
• Expected Outcome:
  • Applications in areas requiring business licenses are flagged accordingly.
  • Applications in prohibited areas are flagged as STR Prohibited and blocked from approval.

🌟 Scenarios:

• BL Requirement:
  Given the property is in an area requiring a business license,
  Then the system flags the application as Business License Required.

• STR Prohibited Area:
  Given the property is in an area where STR is prohibited,
  Then the application is flagged as STR Prohibited.

---

4️⃣ Error Handling During API and Data Checks

• Trigger: API calls fail during the address validation process.
• Expected Outcome:
  • If the API fails, the status defaults to Full Review with corresponding error messages.
  • Provide retry options and prevent incorrect approvals.

🌟 Scenarios:

• API Failure:
  Given the API fails to validate address data,
  Then the system flags the application with Look Up Service Failed and assigns Full Review status.

---

5️⃣ Accessibility Testing

Ensure compliance with accessibility standards for keyboard navigation, screen readers, and low vision users.

🌟 Scenarios:

• Keyboard Navigation:
  Given a keyboard user navigates through the application,
  Then all elements are accessible via Tab and actionable with Enter/Space keys.

• Screen Reader Support:
  Given a screen reader user navigates the application,
  Then all content has appropriate labels and semantic headings.

---

🔑 Business Rules Summary

• Full Review Flags:

  • Applications with Rent ownership or Exempt Accommodation Provider are flagged for Full Review.
  • Applications with Strata Hotel or Farm Land PR exemptions are also sent for Full Review.
  • Applications with STR Prohibited or BL Requirements receive appropriate flags.

• PR Exempt Handling:

  • Auto Approved if PR Exempt.
  • Applied if not PR Exempt or if address is not found.

• Error Handling:

  • If APIs fail, status defaults to Full Review with appropriate flags.

---

🛠️ Exploration Checklist

• [ ] Verify applications with Rent or Exempt Service Provider are flagged for Full Review.
• [ ] Ensure Strata Hotel or Farm Land exemptions trigger Full Examination.
• [ ] Confirm PR Exempt properties are marked as Auto Approved.
• [ ] Validate correct flags for Business License Requirements and STR Prohibited areas.
• [ ] Test API failure handling and ensure status defaults to Full Review with error flags.
• [ ] Ensure accessibility compliance for keyboard and screen reader users.
• [ ] Test seamless status updates across the examiner view.

---

🚀 Goal

Ensure the system correctly flags applications for Full Review or Auto Approval based on property data, exemptions, and ownership. Provide reliable error handling and ensure a smooth user experience with clear statuses and flags.

[rstens]

Tester:

• [ ] Done

Session 1: Flagging for Full Review Based on Ownership and Exemptions

• Focus: Validate that the system correctly flags applications for Full Review based on ownership type and exemption status.
• Scope: Ensure applications are flagged when hosts select "Rent," "Exempt Accommodation Provider," "Strata Hotel," or "Farm Land" as ownership or exemption reasons.
• Goal: Confirm correct flagging for Full Review based on user selections during the application process.

Documentation

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

---

[rstens]

Tester:

• [ ] Done

Session 2: PR Exemption and Automatic Approval

• Focus: Test the logic for PR exemptions and the automatic approval process.
• Scope: Ensure applications flagged as PR Exempt are auto-approved. Validate fallback to Full Review if the property is not PR Exempt or if the address is not found via the API.
• Goal: Confirm correct status changes based on PR exemption logic.

Documentation

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

---

[rstens]

Tester:

• [ ] Done

Session 3: Business License and STR Prohibition Checks

• Focus: Validate the flagging logic for business license requirements and STR prohibitions.
• Scope: Confirm that properties requiring business licenses are flagged appropriately and that applications in prohibited areas are blocked from approval.
• Goal: Ensure applications receive the correct status based on local regulations.

Documentation

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

---

[rstens]

Tester:

• [ ] Done

Session 4: Error Handling During API and Data Checks

• Focus: Test error handling when API calls fail during address validation.
• Scope: Ensure that API failures trigger Full Review status with appropriate error messages. Validate retry options and confirm that the system prevents incorrect approvals.
• Goal: Confirm reliable error handling and fallback logic during API failures.

Documentation

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

---

[rstens]

Tester:

• [ ] Done

Session 5: Accessibility Testing

• Focus: Ensure the system meets accessibility standards for navigation and content.
• Scope: Test keyboard navigation, screen reader compatibility, and high-contrast mode to ensure all content is accessible and properly labeled.
• Goal: Confirm compliance with accessibility standards and seamless navigation for all users.

Documentation

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

---

[rstens]

Tester:

• [ ] Done

Session 6: Business Rules Validation

• Focus: Validate the business rules for Full Review, auto-approval, and flagging logic.
• Scope: Ensure applications are flagged for Full Review based on ownership or exemption reasons, and validate auto-approval for PR Exempt properties. Confirm correct status updates when business licenses are required or STR prohibitions apply.
• Goal: Ensure the system enforces all business rules accurately.

Documentation

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

---

[rstens]

Tester:

• [ ] Done

Session 7: Key Scenarios and Edge Cases

• Focus: Explore edge cases and unexpected scenarios in the flagging logic.
• Scope: Test scenarios such as API failures, address not found, and conflicting ownership or exemption data. Validate seamless status updates across examiner views.
• Goal: Identify potential issues and ensure robust handling of edge cases.

Documentation

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