You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From #111, feedback from Vispero was that it may be hard to get agreement on assertion priority between "should have" and "optional", and we should merge them into only "optional".
I have implemented this change in working mode doc: #41
Assertion priority: Specifies whether an assertion is “must have” or “optional”.
What was the rationale to have "should have" originally? Do people agree that dropping it is a good idea?
The text was updated successfully, but these errors were encountered:
zcorpan
added
feedback
Issue raised by or for collecting input from people outside the core project team.
tests
About assistive technology tests
labels
Mar 11, 2020
zcorpan
changed the title
Change assertion priority to only "must have" and "optional"
Change assertion priority to only "required" and "optional"
Apr 1, 2020
From #111, feedback from Vispero was that it may be hard to get agreement on assertion priority between "should have" and "optional", and we should merge them into only "optional".
I have implemented this change in working mode doc: #41
What was the rationale to have "should have" originally? Do people agree that dropping it is a good idea?
The text was updated successfully, but these errors were encountered: