QA - ETC Review Application

[rstens]

🧭 Exploratory Testing Charter: Examiner - Application Review, LTSA Information, and Approval Process

🎯 Purpose

Explore the Examiner’s functionality to:

1. Review applications in read-only mode and download documents.
2. Access LTSA information and review auto-approval flags.
3. Manage approval, rejection, or decline of applications and validate changes in registration statuses.

---

🔍 Key Areas to Explore

1️⃣ Opening Applications in Read-Only Mode and Document Management

• Trigger: Examiners need to open applications without making changes and download attachments.
• Expected Outcome:
  • Application opens in read-only mode in a new tab.
  • Documents are accessible for download and view.

🌟 Scenarios:

• Scenario 1: Open Application in Read-Only Mode
  Given the examiner is on the dashboard,
  When the examiner clicks on an application,
  Then the application opens in a new tab in read-only mode.

• Scenario 2: Download Attachments
  Given the examiner is viewing an application in read-only mode,
  When the examiner sees a list of documents,
  Then the examiner can click to download each attachment.

---

2️⃣ Accessing and Reviewing LTSA Information

• Trigger: Examiners need to view LTSA data to verify ownership and land details.
• Expected Outcome:
  • LTSA information is visible and detailed (including tax authority, ownership, and tenancy).
  • Information opens in a new tab for review.

🌟 Scenarios:

• Scenario 1: Access LTSA Information
  Given the examiner is viewing an application in read-only mode,
  When the examiner clicks on the LTSA information link,
  Then the LTSA details open in a new tab for review.

---

3️⃣ Reviewing Auto-Approval Logic and Flags

• Trigger: Examiners need visibility into the auto-approval logic and flag history.
• Expected Outcome:
  • The auto-approval section summarizes the approval process and displays status transitions (e.g., "Full Review," "Auto Approved").
  • Each approval step is shown in a new tab with detailed outcomes.

🌟 Scenarios:

• Scenario 1: View Auto-Approval Flags
  Given the examiner is viewing an application in read-only mode,
  When the examiner clicks on the auto-approval link,
  Then the approval process opens in a new tab with details about the logic used.

---

4️⃣ Approving or Declining Applications

• Trigger: Examiners need to approve or decline applications and ensure all changes are accurately recorded.
• Expected Outcome:
  • Approval: Creates a new entry in the Registration table with Active status.
  • Decline: Prompts examiner to Cancel or Suspend any associated registration.

🌟 Scenarios:

• Scenario 1: Approve Application
  Given the examiner is on the application details page,
  When the examiner clicks Approve,
  Then the application status changes to Approved,
  And a new entry is created in the Registration table with Active status.
  And the "Approve" button is greyed out.

• Scenario 2: Decline Approved Application and Cancel Registration
  Given the application is approved with an existing registration,
  When the examiner clicks Decline,
  Then the examiner is prompted to Cancel or Suspend the registration.
  If Cancel is selected, the registration status updates to Canceled.

• Scenario 3: Decline Approved Application and Suspend Registration
  Given the application is approved with an existing registration,
  When the examiner selects Suspend from the decline options,
  Then the registration status updates to Suspended.

---

5️⃣ Viewing Audit Trail and Filing History

• Trigger: Examiners need an audit log to track application changes.
• Expected Outcome:
  • All status changes, examiner actions, and timestamps are recorded in the filing history for transparency.
  • Changes are stored for a minimum of X years.

🌟 Scenarios:

• Scenario 1: View Audit Trail
  Given the examiner is viewing an application,
  When the examiner navigates to the audit trail section,
  Then all changes made to statuses and certificates are listed with timestamps and examiner details.

---

🔑 Business Rules Summary

1. Read-Only Application View:

   • Applications must open in read-only mode with no editing capabilities.
   • Documents uploaded must be downloadable.

2. LTSA Information:

   • LTSA data opens in a new tab and shows ownership, tax, and tenancy details.

3. Auto-Approval Logic:

   • Auto-approval outcomes are displayed row by row, with full review or approval status clearly indicated.

4. Approval and Decline:

   • Approval: Creates a new registration with Active status.
   • Decline: Prompts examiner to Cancel or Suspend registration if it exists.

5. Audit Log and Filing History:

   • All changes are recorded in real-time, with timestamps and examiner details for auditing.

---

🛠️ Exploration Checklist

• [ ] Validate read-only mode and ensure no editing is possible.
• [ ] Confirm document downloads work as expected.
• [ ] Test the LTSA information link and verify that the new tab displays correct data.
• [ ] Check auto-approval logic to ensure correct flags are applied.
• [ ] Validate approval/decline functionality and ensure registration statuses are correctly updated.
• [ ] Ensure audit logs capture all changes with timestamps and examiner names.

---

🌐 Accessibility Scenarios

1. Keyboard Navigation

   • Given a keyboard user accesses the application,
   • Then all elements (links, buttons) must be navigable via Tab and activated with Enter/Space keys.

2. Screen Reader Support

   • Given a screen reader user navigates the application,
   • Then all elements (documents, status changes) must be announced properly.

3. High Contrast Mode

   • Given a user with low vision enables high contrast mode,
   • Then the UI should remain coherent and readable.

---

🚀 Goal

Ensure the Examiner Dashboard provides a seamless experience for reviewing applications, managing registrations, and auditing changes while maintaining accessibility for all users.

[rstens]

Tester: Andy

• [x] Done

Session 1: Opening Applications in Read-Only Mode and Document Management

• Focus: Validate the behavior of opening applications in read-only mode and downloading attachments.
• Scope: Ensure applications open in a new tab without editing capabilities. Confirm that uploaded documents are accessible and downloadable.
• Goal: Ensure examiners can efficiently view applications and manage attachments without making changes.

Documentation

Time Spent: 5 min

What did you Test?

• [ ] Ensure applications open in a new tab without editing capabilities.
• [x] Confirm that uploaded documents are accessible and downloadable.

Any Observations You Want to Share?

• UX: Application does not open in a new tab, failing the testing goal. However, this is the preferred behaviour, especially with the breadcrumb in place.

Bug Report References:

---

[rstens]

Tester: Mikaela

• [ ] Done

Session 2: Accessing and Reviewing LTSA Information

• Focus: Test the ability to access and review LTSA information related to ownership, tax authority, and tenancy.
• Scope: Confirm that LTSA data opens in a new tab and displays all relevant information for verification purposes.
• Goal: Ensure examiners can access and accurately review LTSA data for decision-making.

Documentation

• Time Spent:
• What did you Test? I created a new user in BC Registries Test environment for the user who is LTSA.
• Any Observations You Want to Share? Need to wait for it to load the LTSA stuff.. will go back and check it. used TERRY EDMUND
  https://bcgov.sharepoint.com/:x:/r/teams/09399/Shared%20Documents/Product-Scrum%20Team%20Chat/LTSA%20Test%20Accounts.csv?d=w93c41235b128494b9adfd5593814c554&csf=1&web=1&e=c8RgGI
• Bug Report References:

---

[rstens]

Tester:

• [ ] Done

Session 3: Reviewing Auto-Approval Logic and Flags

• Focus: Validate the display of auto-approval logic and flag history.
• Scope: Ensure the system shows approval steps in detail, including "Full Review" and "Auto Approved" status transitions.
• Goal: Ensure the auto-approval process is transparent and easy to track.

Documentation

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

---

[rstens]

Tester: Andy

• [x] Done

Session 4: Approving or Declining Applications

• Focus: Test the approval and decline processes, ensuring changes to registration statuses are accurately applied.
• Scope: Confirm that approvals create new entries with "Active" status and that declines prompt the examiner to cancel or suspend registrations.
• Goal: Ensure examiners can manage approvals and declines seamlessly while maintaining accurate status records.

Documentation

Time Spent: 10 min

What did you Test?

• [x] Confirm that approvals create new entries with "Active" status
• [ ] Confirm that declines prompt the examiner to cancel or suspend registrations

Any Observations You Want to Share?

• No ability to decline an approved application.

Bug Report References:

---

[rstens]

Tester: Andy

• [ ] Done

Session 5: Viewing Audit Trail and Filing History

• Focus: Validate the accuracy and completeness of the audit trail.
• Scope: Ensure all actions, including status changes and examiner inputs, are recorded with timestamps and examiner names.
• Goal: Ensure transparency in application management and compliance with audit requirements.

Documentation

Time Spent: 20 min

What did you Test?

• [x] Test if all status changes, examiner actions, and timestamps are recorded in the filing history for transparency.
• [ ] Test if changes are stored for a minimum of X years.

Any Observations You Want to Share?
🟡 Issuing a certificate is recorded in the Filing History ONLY on the Registration Details page (but the CTA to issue certificate is ONLY on the Application Details page) ❌ Filing History on the Registration Details page is displayed in the wrong order (should be reverse chronological) ❓ No idea how to test how long the Filing History is stored for

Bug Report References:

---

[rstens]

Tester:

• [ ] Done

Session 6: Accessibility Testing

• Focus: Ensure accessibility compliance for the application review interface.
• Scope: Validate keyboard navigation, screen reader compatibility, and high-contrast mode functionality to ensure the dashboard is accessible to all users.
• Goal: Ensure a seamless experience for users with disabilities, following WCAG 2.1 standards.

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 key scenarios and potential issues in application review and approval processes.
• Scope: Test scenarios such as incorrect LTSA data, failed approvals, and interrupted session handling. Confirm consistent behavior across all scenarios.
• Goal: Identify potential issues or inconsistencies and ensure robust handling of edge cases.

Documentation

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

---

[rstens]

Tester:

• [ ] Done

Session 8: Usability and Performance Testing

• Focus: Validate the dashboard's usability and performance under different conditions.
• Scope: Test the behavior of approvals, declines, and document management under varying network conditions. Ensure that the UI remains responsive and intuitive.
• Goal: Ensure smooth and efficient performance across all environments and device types.

Documentation

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