Skip to content
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

[ci] Generate unit test coverage on PR #759

Merged
merged 1 commit into from
Sep 13, 2024

Conversation

ian-shim
Copy link
Contributor

@ian-shim ian-shim commented Sep 12, 2024

Why are these changes needed?

  • bumps actions/download-artifact version
  • prints new test coverage in unit-tests action
  • adds a check in PR template to confirm the PR doesn't impair coverage

Checks

  • I've made sure the lint is passing in this PR.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, in that case, please comment that they are not relevant.
  • Testing Strategy
    • Unit tests
    • Integration tests
    • This PR is not tested :(

@ian-shim ian-shim force-pushed the generate-coverage-on-pr branch 2 times, most recently from 5523cb0 to e6276f6 Compare September 12, 2024 15:48
@ian-shim ian-shim marked this pull request as ready for review September 12, 2024 16:47
@@ -6,6 +6,7 @@

- [ ] I've made sure the lint is passing in this PR.
- [ ] I've made sure the tests are passing. Note that there might be a few flaky tests, in that case, please comment that they are not relevant.
- [ ] I've checked the new test coverage and the coverage percentage didn't drop.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's nice if coverage can be at least maintained in each PR, but it may be too difficult (passing lint and unit tests on the other hand are must)

@ian-shim ian-shim merged commit 0d64c9a into Layr-Labs:master Sep 13, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants