QA -ETC Examiner Dashboard

[rstens]

🧭 Exploratory Testing Charter: Examiner Dashboard - Application Filtering and Table View

🎯 Purpose

Explore the functionality of the Examiner Dashboard to ensure seamless filtering of applications and an intuitive table view. Validate that examiners can use filters and table features to manage their workload efficiently.

---

🔍 Key Areas to Explore

1️⃣ Filtering Applications by Status

• Trigger: Examiners need to filter applications by All, Full Review, or Provisional Approval.
• Expected Outcome:
  • Examiners can narrow their application list by selecting a status filter.
  • All filter is applied by default on login.
  • A loading indicator should display while applications load.

🌟 Scenarios:

• Scenario 1: Viewing All Applications
  Given the examiner is logged in,
  When the examiner selects All from the filter dropdown,
  Then the dashboard should display all applications without filtering.

• Scenario 2: Viewing Applications Under Full Review
  Given the examiner is logged in,
  When the examiner selects Full Review from the filter dropdown,
  Then only applications under Full Review are displayed.

• Scenario 3: Viewing Applications with Provisional Approval
  Given the examiner is logged in,
  When the examiner selects Provisional Approval from the dropdown,
  Then only applications with Provisional Approval are shown.

---

2️⃣ Table View for Application Management

• Trigger: Examiners need a simple table view with critical application details.
• Expected Outcome:
  • Applications should display in a paginated table with essential information.
  • The examiner can click any row to open the application details.

🌟 Scenarios:

• Scenario 1: Table Display on Login
  Given the examiner logs in with IDIR,
  Then the dashboard displays a table view with the following columns:

  • Registration #
  • Location (City)
  • Property Address
  • Applicant Name (Primary Contact)
  • Status (default: "Applied")
  • Submission Date (when payment is successfully made)

• Scenario 2: Pagination for Large Datasets
  Given there are many applications to display,
  When the examiner navigates between pages,
  Then the system loads applications with a loading indicator during transitions.

• Scenario 3: Accessing Application Details
  Given the examiner is viewing the table,
  When the examiner clicks anywhere on a row,
  Then the application details view opens.

---

3️⃣ Viewing Registration Numbers for Approved Applications

• Trigger: Examiners need visibility into registration numbers for approved applications.
• Expected Outcome:
  • Registration numbers should be visible for provisionally approved or automatically approved applications.

🌟 Scenario: Displaying Registration Numbers

• Given the application has been approved,
• When the status is Provisional Approval or Auto Approved,
• Then the registration number should be visible in the table under the appropriate column.

---

🔑 Business Rules Summary

• Filtering:

  • Three filters: All, Full Review, Provisional Approval.
  • All filter is the default on login.
  • Loading indicator must display while applications load.

• Table View:

  • The table includes Registration #, Location, Address, Applicant Name, Status, Submission Date.
  • Pagination should enable easy navigation through large datasets.
  • Row click opens the application details view.

• Registration Numbers:

  • Visible only for provisionally or automatically approved applications.

---

🛠️ Exploration Checklist

• [ ] Validate the behavior of filters (All, Full Review, Provisional Approval).
• [ ] Confirm All filter is applied by default on login.
• [ ] Ensure loading indicators display while applications load.
• [ ] Verify the table view displays the correct columns and data.
• [ ] Test pagination for large application datasets.
• [ ] Confirm clicking a row opens the application details view.
• [ ] Ensure registration numbers appear for approved applications.

---

🌐 Accessibility Scenarios

1. Keyboard Navigation

   • Given a keyboard user interacts with the dashboard,
   • Then all elements (filters, table rows) must be navigable via Tab and actionable via Enter/Space keys.

2. Screen Reader Support

   • Given a screen reader user interacts with the dashboard,
   • Then all filters and table data must be announced appropriately.

3. High Contrast Mode

   • Given a user with low vision uses high contrast mode,
   • Then the layout should remain readable and accessible.

---

🚀 Goal

Ensure the Examiner Dashboard provides efficient filtering, easy application management, and clear access to approved application registration numbers. Maintain seamless accessibility and usability for all users.

[rstens]

Tester: @fionazhou-jsb

• [x] Done

Session 1: Filtering Applications by Status

• Focus: Validate the functionality of the status filters on the Examiner Dashboard.
• Scope: Ensure that the "All" filter is applied by default, and filters for "Full Review" and "Provisional Approval" work as expected. Confirm the display of a loading indicator during filter changes.
• Goal: Ensure that the filtering mechanism is intuitive, responsive, and effective for workload management.

Documentation

• Time Spent: 5 mins
• What did you Test? login as examiner on the dashboard, view applications in the table view, clicked tabs to see applications in different status, checked the count on each status tab
• Any Observations You Want to Share? filter and sort are not available. Pagination can be improved a bit. For example, show 10/20/100 records per page. Search is quite helpful.
• Bug Report References: n/a

---

[rstens]

Tester: @fionazhou-jsb

• [x] Done

Session 2: Table View for Application Management

• Focus: Validate the table view for displaying critical application information.
• Scope: Ensure that the table displays key details such as Registration #, Location, Property Address, Applicant Name, Status, and Submission Date. Confirm that pagination works smoothly with a loading indicator during page transitions.
• Goal: Ensure the table provides an efficient way to manage applications, with smooth transitions and easy access to details.

Documentation

• Time Spent: 15 mins
• What did you Test? sorting, search, showing certain columns, pagination
• Any Observations You Want to Share? search works quite well. Search only search the application under that status.
• Bug Report References: sorting is not working #23972, switching from tabs is not working #23978

---

[rstens]

Tester: Andy

• [x] Done

Session 3: Viewing Registration Numbers for Approved Applications

• Focus: Test the visibility of registration numbers for approved applications.
• Scope: Ensure that registration numbers are displayed for provisionally and automatically approved applications. Confirm that the numbers are visible only under the appropriate column.
• Goal: Ensure accurate and accessible display of registration numbers for relevant applications.

Documentation

Time Spent: 5 min

What did you Test?

• [x] Ensure that registration numbers are displayed for approved applications.
• [x] Confirm that the numbers are visible only under the appropriate column.

Any Observations You Want to Share?

Bug Report References:

---

[rstens]

Tester:

• [ ] Done

Session 4: Accessibility Testing

• Focus: Validate the accessibility of the dashboard, ensuring compliance with standards for screen readers, keyboard navigation, and high-contrast mode.
• Scope: Test that all elements (filters, table rows, pagination) are accessible via Tab, Enter, and Space keys. Confirm that screen readers correctly announce filters and table content. Ensure high-contrast mode preserves readability and layout.
• Goal: Ensure the dashboard is usable and accessible to all users, including those with disabilities.

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 the business rules governing filters, table view, and registration number visibility.
• Scope: Confirm the correct application of the "All" filter by default and validate the behavior of other filters. Ensure registration numbers only appear for provisionally or automatically approved applications.
• Goal: Ensure that all business rules are implemented correctly and function as intended.

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 key scenarios and potential issues in filtering, pagination, and table view behavior.
• Scope: Test scenarios such as switching between filters, managing large datasets, and opening application details from different rows. Validate the dashboard’s behavior under interrupted network conditions.
• 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:

---