Skip to content

Conversation

@mbuechse
Copy link
Contributor

No description provided.

Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
Copy link
Contributor

@depressiveRobot depressiveRobot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work! Thank you for implementing the idea of deep linking the corresponding standard for each test (see #1055) :)

@mbuechse
Copy link
Contributor Author

Nice work! Thank you for implementing the idea of deep linking the corresponding standard for each test (see #1055) :)

But you realize that's not what I've done? I couldn't deep link to the standard because I wouldn't know which version of the standard to link to. Therefore I linked to the testing notes (which should apply to all (recent) versions)

@depressiveRobot depressiveRobot self-requested a review January 30, 2026 09:16
@mbuechse mbuechse merged commit 91effc1 into main Jan 30, 2026
8 checks passed
@mbuechse mbuechse deleted the feat/improve-testcase-docs branch January 30, 2026 09:21
@depressiveRobot
Copy link
Contributor

Oops, I missed that. But you are right. As the same test can be in different versions of the standard and sometimes required or recommended, the link to the testing notes seems to be a good tradeoff. This way one can also get quickly to the standard itself using the navigation.

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

Successfully merging this pull request may close these issues.

4 participants