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