8000 V2 Summary Test Suite Links Do Not Work · Issue #566 · dorny/test-reporter · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

V2 Summary Test Suite Links Do Not Work #566

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

Closed
micmarc opened this issue Mar 25, 2025 · 1 comment · Fixed by #567
Closed

V2 Summary Test Suite Links Do Not Work #566

micmarc opened this issue Mar 25, 2025 · 1 comment · Fixed by #567
Assignees
Labels
bug Something isn't working

Comments

@micmarc
Copy link
Contributor
micmarc commented Mar 25, 2025

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:

  1. Run a build with a Test Reporter step that uses V2 and the java-junit report format
  2. Navigate to the build summary to view the test report
  3. Scroll down to the test results
  4. Click on one of the test suite links
  5. 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.
Image

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

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.

@micmarc micmarc added the bug Something isn't working label Mar 25, 2025
@micmarc
Copy link
Contributor Author
micmarc commented Mar 25, 2025

This discussion looks promising: https://github.com/orgs/community/discussions/129877

I did some manual testing by prepending user-content- to the existing links and it seems to work. I'll see if I can open a PR to fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants
0