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
When using the java-junit report format, the generated summary includes a table with links for every test suite. However, these links do not work due to invalid anchors.
To Reproduce
Steps to reproduce the behavior:
Run a build with a Test Reporter step that uses V2 and the java-junit report format
Navigate to the build summary to view the test report
Scroll down to the test results
Click on one of the test suite links
Observe that nothing happens
Expected behavior
When I click on test suite links in the table, it should take me to the detailed report for that test suite.
Screenshots
When I click the link indicated by the red arrow below, the URL updates but the page does not scroll.
It should take me to the detailed view shown here, but it does not:
Additional context
I am using this with a Python (Django) project and unittext-xml-reporting but I don't think that matters. This seems to be due to differences in how anchors are generated in GitHub Actions build summaries vs. Check reports.
The text was updated successfully, but these errors were encountered:
Describe the bug
When using the
java-junit
report format, the generated summary includes a table with links for every test suite. However, these links do not work due to invalid anchors.To Reproduce
Steps to reproduce the behavior:
java-junit
report formatExpected behavior
When I click on test suite links in the table, it should take me to the detailed report for that test suite.
Screenshots
When I click the link indicated by the red arrow below, the URL updates but the page does not scroll.

It should take me to the detailed view shown here, but it does not:

Additional context
I am using this with a Python (Django) project and
unittext-xml-reporting
but I don't think that matters. This seems to be due to differences in how anchors are generated in GitHub Actions build summaries vs. Check reports.The text was updated successfully, but these errors were encountered: