Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Report Status" UI oversimplifies the state of Test Plan Runs #1046

Open
jugglinmike opened this issue Apr 8, 2024 · 1 comment
Open

"Report Status" UI oversimplifies the state of Test Plan Runs #1046

jugglinmike opened this issue Apr 8, 2024 · 1 comment
Assignees

Comments

@jugglinmike
Copy link
Contributor

Today, given a Test Plan Run with 3 tests and 6 assertions (where the NVDA Bot has collected all 3 AT responses and assigned 0 verdicts), the "Report Status" dialog will report "100% complete by NVDA Bot with 0 conflicts." This is misleading because the verdicts are absent, so they cannot be in conflict or in alignment with those in other Test Plan Runs.

Here are some potential solutions:

  • Treat unassigned verdicts as inherently conflicting. In the situation described above, the status text would instead read, "100% complete by NVDA Bot with 6 conflicts"
  • Extend the status text to fully document the relevant state. In the situation described above, the status text would instead read, "100% complete by NVDA Bot with 0 conflicts and 6 missing verdicts"
@ccanash
Copy link
Contributor

ccanash commented Apr 9, 2024

Hi @mcking65 @mfairchild365, do you agree this is an issue and do you have a preference for either of these solutions or a third option?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants