-
Notifications
You must be signed in to change notification settings - Fork 15
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
Version histories are showing incorrect deprecation dates #966
Comments
As agreed in another discussion, the above is a one issue and the rest of the top comment is another so they will be handled separately. |
…1122) Address #966 --------- Co-authored-by: Howard Edwards <[email protected]>
The last deployment of the app broke an important working mode requirement.
The deprecation date of a test plan that was deprecated during candidate review should be the same date that the newer version was advanced to candidate. There are several test plans where the deprecation date of plans deprecated during candidate review are incorrect.
I remember spending a lot of time checking this functionality for nearly all test plans last summer, and I believe we resolved all inconsistencies. Now it appears there are regressions in the functionality and data has changed in unexpected ways.
For example, look at the alert example on the candidate review page. It shows that the candidate review start date is Jan 11, 2024.
However, you can see from the timeline for all versions of the alert test plan that candidate review of the alert test plan started on Dec 9, 2022 when V22.12.08 advanced to candidate.
While the alert plan has the correct deprecation date for v22.12.08 when V23.12.06 was advanced to candidate review, there are other test plans where the deprecation date is inconsistent with other dates in the timeline. For example, look at the Disclosure Navigation Menu Example Test Plan.
For this test plan, the timeline shows that Candidate Review Started on Dec 1, 2021 when V21.11.30 advanced to candidate. The timeline also shows that V21.11.30 was deprecated on Dec 1, 2021. Look further down the timeline and you can see that the next version to advance to candidate was V22.10.31 on Nov 1, 2022. So, that should be the deprecation date for V21.11.30. In addition, the candidate review and data management pages show that candidate review started on Nov 1, 2022 but the versions timeline shows that candidate review started Dec 1, 2021. I question that Dec 1, 2021 date, though; I don't remember when we first advanced a plan to candidate, but that seems earlier than I recall. At any rate, the timeline is inconsistent.
Similarly, in the Radio Group Example Using aria-activedescendant Test Plan, the deprecation date for the version that was deprecated when V23.04.10 advanced to candidate is incorrect. V23.04.10 advanced to candidate on Apr 11, 2023. When it advanced, it deprecated V22.05.18. However, the deprecation date shown for V22.05.18 is Dec 8, 2022, but it should be Apr 11, 2023. The data management and candidate review pages show that candidate review started on Apr 11, 2023, but it actually started on May 19, 2022.
The text was updated successfully, but these errors were encountered: