-
Notifications
You must be signed in to change notification settings - Fork 0
[WIP] Report Unit tests results #12
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
Conversation
|
@copilot please try again |
Co-authored-by: tspascoal <7847935+tspascoal@users.noreply.github.com>
I've implemented the unit test results reporting as requested in issue #11. The solution includes:
The implementation is now ready for testing. Changes are in commit 33e7c82. |
|
@copilot This is great. Can you please update the README.md to reflect the CI changes that were made? |
Co-authored-by: tspascoal <7847935+tspascoal@users.noreply.github.com>
I've updated the README.md to document the CI changes for unit test results reporting. The updated Continuous Integration section now explains how both GitHub Actions and Azure Pipelines publish test results, including the Jest JUnit XML configuration. Changes are in commit 5f30df3. |
|
@copilot Great. Test reporting is working, now please do the same for code coverage |
Co-authored-by: tspascoal <7847935+tspascoal@users.noreply.github.com>
I've implemented code coverage reporting for both GitHub Actions and Azure Pipelines, following the same pattern as test results reporting. The implementation includes:
Coverage reports are published even if tests fail, providing visibility into coverage metrics alongside test results. Changes are in commit ed76abc. |
|
Minimum allowed coverage is Generated by 🐒 cobertura-action against 539cd42 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This pull request implements unit test and code coverage reporting for both GitHub Actions and Azure Pipelines CI workflows. The changes add JUnit XML test reporting and Cobertura coverage reporting to provide visibility into test results and coverage metrics in pull request comments and CI dashboards.
- Configures Jest to output JUnit XML format for test results and Cobertura XML format for coverage reports
- Adds GitHub Actions workflow steps to publish test results as PR comments using
dorny/test-reporterand coverage results using5monkeys/cobertura-action - Adds Azure Pipelines tasks to publish test results and coverage reports in the pipeline dashboard
Reviewed Changes
Copilot reviewed 5 out of 7 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| create-github-app-token/package.json | Adds jest-junit dependency and reorganizes devDependencies |
| create-github-app-token/jest.config.js | Configures JUnit XML reporting and adds Cobertura coverage format |
| azure-pipelines.yml | Adds tasks to publish test results and code coverage in Azure Pipelines |
| README.md | Documents the new test reporting and coverage features in CI workflows |
| .github/workflows/ci.yml | Adds GitHub Actions steps for test and coverage reporting with required permissions |
Files not reviewed (1)
- create-github-app-token/package-lock.json: Language not supported
Thanks for assigning this issue to me. I'm starting to work on it and will keep this PR's description up to date as I form a plan and make progress.
Original issue description:
Fixes #11.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.