[Feature Request] Native Test Results Dashboard for GitHub Actions (like Azure DevOps)

[Mark-Halstead]

Why are you starting this discussion?

Product Feedback

What GitHub Actions topic or product is this about?

Metrics & Insights

Discussion Details

Feature Request: Enhanced Native Test Results Reporting for GitHub Actions

Current Limitations

GitHub Actions currently lacks a native UI for viewing test results comprehensively. Test outcomes are either displayed in logs or as artifacts, and while third-party actions like dorny/test-reporter offer some functionality by parsing JUnit/XML results and generating markdown summaries or GitHub Check annotations, they have significant limitations:

• No Dedicated UI: There is no first-class UI for test results, leading third-party tools to use markdown summaries for log display.
• Limited Interactivity: Reports from third-party tools are static and do not allow users to interactively navigate through individual test results.
• Annotation Limits: GitHub imposes a limit of 50 annotations per job.
• Long-term Support Concerns: Dependency on community-maintained actions introduces risks if the maintainer ceases updates or if there are API changes.

There is clear demand for a more integrated solution, as highlighted by user feedback:

• Sean Killeen’s Blog on .NET Test Reports
• GitHub Community Discussion #161841

Proposed Feature

To close this gap, GitHub Actions would benefit from a native test results reporting UI modeled on: Azure DevOps Test Results Review:

1. Test Summary Dashboard
   Display key metrics upon workflow completion: total number of tests, number passed/failed/skipped, overall pass percentage, and visual cues (charts and icons).

2. Results List with Filtering Options
   Show a detailed list of all test cases run, with the ability to filter by outcome (passed/failed/skipped) or by test name/id or test suite.

3. Interactive Test Details
   Enable clicking on test names to view full logs, debug logs, error messages, stack traces, and attachments, emulating Azure DevOps functionality.

   

4. Unique Test Identifiers
   Include identifiers like run-id and resultId for precise tracking.

5. Native Integration with GitHub Checks
   Incorporate a test summary dashboard in the GitHub Checks UI to display overall test outcomes.

Benefits

1. Faster Troubleshooting
   Immediate visibility into individual failed tests and structured failure details aids quicker resolution.

2. Enhanced User Experience
   Aligns GitHub Actions with features available on platforms like Azure DevOps.

3. Quality Focus
   Detailed views of each test facilitate a deeper understanding and monitoring of test performance. Additionally, comparisons with historic test runs enable test traceability.

4. Reduced Dependency on Third-Party Tools
   Integrates essential functionalities natively, reducing the need for external plugins.

5. Long-term Extensibility
   Supports future enhancements and integrations within GitHub Actions.

Conclusion

Implementing native test reporting in GitHub Actions would significantly enhance the developer experience and the CI feedback loop. It addresses a widely requested feature and aligns GitHub Actions with other leading CI platforms such as Azure DevOps, offering a comprehensive, built-in solution for managing test results effectively.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[chamithgithub]

💬 Product Feedback: GitHub Projects Beta
👍 What I liked:
The new layout and filtering options make it much easier to manage large teams.
⚠️ What could be improved:
There’s no way to set default filters per user or save personal views. It resets every time I visit the board.
💡 Suggested improvement:
Allow users to save custom views or remember last used filters.
📘 Use case:
I’m managing multiple issue boards across teams and need to focus on issues assigned to me or in specific status columns daily.

[Jayesh-Kamble]

Great idea! 👍 As someone who's been juggling between different CI/CD platforms, this would be a game-changer for GitHub Actions.

The current workaround of digging through logs or setting up third-party tools just to see which tests failed is honestly pretty painful. Having a native dashboard like Azure DevOps would save so much time during debugging.

A few thoughts to add:

• Maybe include test execution time trends over commits?
• Could we get flaky test detection (tests that pass/fail inconsistently)?
• Integration with GitHub Issues to auto-create tickets for consistently failing tests?

This would definitely help GitHub Actions compete better with other platforms. Hope the team considers this - it's exactly what many of us have been waiting for!

[nazamey]

While GitHub Actions doesn't yet offer a native test-results dashboard like Azure DevOps, you can achieve similar functionality using third-party tools and custom configurations. Here's a practical workaround:
Use actions/upload-artifact + test reporter tools
Generate test results in JUnit or other supported formats in your CI workflow.

Upload test reports as artifacts using actions/upload-artifact.

Optionally parse and display them using tools like:
1- dorny/test-reporter
2- Allure can generate full HTML dashboards with trends and interactive test logs.
3- Host reports via GitHub Pages or upload as build artifacts for download.
Hope this helps others looking for an immediate solution!

[httpashu]

Here's a clear, constructive, and supportive comment you can post on the GitHub Discussion or relevant issue thread to back the feature request and add your voice as a user:

---

🚀 Strong Support for Native Test Reporting UI in GitHub Actions

I wholeheartedly support this feature request.

As it stands, the current approach to test result reporting in GitHub Actions is fragmented and heavily reliant on community-maintained actions like dorny/test-reporter. While useful, these tools are limited by:

• Lack of a dedicated UI
• Annotation caps (50/job)
• Static, non-interactive output
• Uncertainty around long-term maintenance

✅ Why a Native Test Results UI Matters
A native, first-class UI—similar to what Azure DevOps offers—would be a huge productivity boost. It would:

• Offer clear visibility into test outcomes (passed/failed/skipped)
• Help debug failures faster with full logs, stack traces, and error messages
• Allow filtering by test status, name, or suite
• Integrate seamlessly with GitHub Checks for improved developer experience

📊 Dev-Focused Insight Dashboard
A dashboard view that summarizes test metrics at a glance would be ideal for:

• CI feedback loops
• Quality monitoring
• Regression tracking

🔒 Bonus: Less Reliance on Third Parties
Native features reduce risk from third-party tool deprecation and API breakages, especially in enterprise or mission-critical workflows.

GitHub Actions has evolved into a powerful CI/CD tool—this improvement would take it even further. Would love to see this on the roadmap. 👏

---

[Dasmat13]

I wanted to bring up a feature request that I think would really improve the experience of using GitHub Actions: a native UI for test result reporting.

Right now, GitHub Actions doesn’t offer a built-in way to view test results in a clear and structured format. We're mostly left with logs, downloadable artifacts, or third-party actions like dorny/test-reporter. While those tools are helpful, they come with a few challenges:

No dedicated test results UI — everything gets dumped into logs or markdown.

The reports are static — you can’t filter or drill down into specific tests.

GitHub limits the number of annotations per job (currently 50), which is tough for larger test suites.

Third-party tools can be hit or miss in terms of long-term support or compatibility.

I think there's a real opportunity here for GitHub to offer something similar to Azure DevOps or other CI tools — a native test reporting dashboard inside Actions.

Some ideas:

A test summary showing total tests, how many passed/failed/skipped, and overall success rate.

A filterable list of all test cases with pass/fail status.

Clickable test entries that show error logs, stack traces, and maybe even debug info.

Integration with the GitHub Checks UI, so test results are easily visible alongside code reviews.

This would save a lot of time during debugging and improve the overall CI/CD experience. It would also reduce the need to rely on third-party actions just to view test results properly.

[ritikkumar8z]

✅ Response:
Hi 👋 — thanks for the suggestion!

• I absolutely agree — a native test results dashboard for GitHub Actions would be incredibly valuable. While we currently rely on third-party tools (like JUnit, Test Report, or Allure integrations), they often require extra setup and aren't as seamless or visually integrated as Azure DevOps or GitLab's built-in test reporting.

A built-in UI for:

• Aggregating test results from popular formats (e.g. JUnit, NUnit, Mocha, etc.)
• Showing pass/fail trends over time
• Surfacing flaky or frequently failing tests
• Navigating test failures directly from workflow runs

...would really improve the developer experience, especially for larger teams working with CI/CD on a daily basis.

It would also align well with GitHub Actions' goal of being a first-class DevOps platform. I'd love to see this feature on the roadmap!

Thanks again for raising this — +1 from me!

[manasdutta04]

Test dashboards in GitHub Actions? Yes please!

Right now, checking test results in GitHub Actions feels like trying to find a needle in a haystack... except the haystack is made of logs, and the needle is your sanity.

A native test results dashboard would be a massive win:

• ✅ See test pass/fail summaries at a glance

• 📉 Spot flaky tests and runtime regressions over time

• 💡 Avoid installing Yet Another Third-Party Tool™ just to know what broke

Here's what I'd love to see:

• Built-in support for common test formats (JUnit, TAP, etc.)
• A dedicated “Tests” tab on each workflow run (just like the “Artifacts” tab)
• Aggregate test trends at the repo level (maybe with sparklines? ✨)

CI without visibility is just... blind deployment with extra steps. Let’s make GitHub Actions as dev-friendly as it is powerful.

🚀 Hope the GitHub team gives this serious thought—this feature would help thousands of teams (and save millions of log-scrolls).

Upvote this if you’ve ever shouted “WHICH TEST FAILED?!” at your screen. 🙃

[Ranjeet6639]

This is an excellent and much-needed feature request — I completely agree with the points raised here.

Having a native test results dashboard (similar to Azure DevOps) would significantly improve the developer and reviewer experience in GitHub Actions. Some specific benefits I see:

• Faster debugging and PR reviews — No need to dig through logs to understand which test failed.

• Better visibility for QA and team leads — A high-level summary with pass/fail counts helps track test health across workflows.

• Improved onboarding — Developers new to a repo can instantly understand test results without parsing raw logs.

It would also be great if this dashboard could:

• Integrate with common formats like JUnit, NUnit, and TestNG.

• Support inline annotations in PRs for failed tests.

• Work seamlessly across both monorepos and microservice repos.

Fully support this idea — I hope GitHub considers it for future roadmap inclusion!

[zbyte64]

In the mean time I am using CTRF: https://github.com/ctrf-io/github-test-reporter

[eduardogoncalvestech]

This is a great and well-articulated feature request. The lack of a native test results UI in GitHub Actions is definitely something that many developers feel in day-to-day workflows.

Today, relying on logs, artifacts, or third-party tools creates fragmentation in the developer experience. While tools like test reporters help, they don’t fully solve the problem—especially due to limitations like static outputs, annotation caps, and long-term maintenance risks.

The proposal for a native solution—particularly with a test summary dashboard, filterable results list, and interactive test details—would significantly improve usability. Having something similar to Azure DevOps would make debugging faster and reduce the friction in CI pipelines.

I also strongly agree that integrating this into GitHub Checks would be a key improvement, since that’s already where developers expect to see high-level feedback.

Overall, this would:

Improve visibility into test results
Speed up troubleshooting
Reduce dependency on third-party actions
Bring GitHub Actions closer to parity with other CI platforms

Hope this gets considered—this is a high-impact improvement for the ecosystem.