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
Using the "Raise An Issue" button throughout the aria-at-app's test run page creates issues here with the incorrect sequence number.
These buttons are found on:
aria-at.w3.org/run/<id>
aria-at.w3.org/candidate-test-plan/<id>/<id>
aria-at.w3.org/report/<id>/targets/<id>
This probably happens because the app is using the presentationNumber value coming from tests.csv rather than using the generated sequence number when presented through the app.
This makes it confusing when reviewing issues created by the app and the issue claims it as being "Test 6" when the app reports the it as "Test 2" on any relevant pages which show a numbered sequence in the app.
To be clear - the "Test Number" should reference what is displayed on aria-at-app, however the presentationNumber of the test is probably still useful information to the aria-at maintainer and should be included in the issue text somewhere I think.
Using the "Raise An Issue" button throughout the aria-at-app's test run page creates issues here with the incorrect sequence number.
These buttons are found on:
<id>
<id>
/<id>
<id>
/targets/<id>
This probably happens because the app is using the
presentationNumber
value coming fromtests.csv
rather than using the generated sequence number when presented through the app.This makes it confusing when reviewing issues created by the app and the issue claims it as being "Test 6" when the app reports the it as "Test 2" on any relevant pages which show a numbered sequence in the app.
This was raised in the May 22, 2024 CG meeting.
The text was updated successfully, but these errors were encountered: