Feature Request: Native Test Results Dashboard in GitHub Actions

[eduardogoncalvestech]

Why are you starting this discussion?

Product Feedback

What GitHub Actions topic or product is this about?

Metrics & Insights

Discussion Details

One recurring pain point when working with GitHub Actions is the lack of a native and interactive interface for test results.

Currently, developers must rely on logs, artifacts, or third-party actions to visualize test outcomes. While solutions like test reporters help, they introduce limitations such as static reports, annotation caps, and dependency on external maintenance.

Problem
No native UI for test results
Poor visibility into failed tests
Limited interactivity (cannot easily drill down into specific test cases)
Fragmented experience across logs, artifacts, and external tools
Suggestion

Introduce a native test results dashboard within GitHub Actions, including:

Test summary view (total, passed, failed, skipped, pass rate)
Filterable test list (by status, name, suite)
Clickable test details (logs, errors, stack traces)
Integration with GitHub Checks UI
Support for common formats (JUnit, XML, etc.)
Why this matters
Faster debugging and troubleshooting
Better developer experience
Reduced reliance on third-party actions
Aligns GitHub Actions with other CI platforms
Conclusion

Adding native test reporting would significantly improve the CI feedback loop and make GitHub Actions more powerful and developer-friendly.

[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. ⭐

[Ankit-Sharma1011]

This is something I’ve wanted as well. Jumping between logs and external tools can be frustrating, so having everything in one place would be really helpful.