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

Do not show 0-priority assertions in the results collection form #1008

Closed
mcking65 opened this issue Dec 3, 2023 · 1 comment
Closed

Do not show 0-priority assertions in the results collection form #1008

mcking65 opened this issue Dec 3, 2023 · 1 comment
Assignees
Labels
bug Something isn't working javascript Pull requests that update Javascript code

Comments

@mcking65
Copy link
Contributor

mcking65 commented Dec 3, 2023

Add support for 0-priority assertions in the test collection form. This means that they should not be included in the collection form.

Example, the assertion

JAWS switched from virtual cursor active to PC cursor active

in JAWS Trigger an alert.

Originally posted by @mcking65 in #997 (review)

@mcking65
Copy link
Contributor Author

I have verified that previews of unmerged test plans with 0 priority assertions work correctly. There are no merged test plans with that characteristic, so I don't know how to verify the runner presentation.

@ccanash ccanash moved this from In sandbox to In production / Completed in Refactor ARIA-AT test structure and test result presentation project Mar 11, 2024
@ccanash ccanash closed this as completed Mar 11, 2024
@ccanash ccanash moved this from In Progress to In production / Completed in Refactor ARIA-AT test structure and test result presentation project Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working javascript Pull requests that update Javascript code
Projects
Development

No branches or pull requests

3 participants