Skip to content

Conversation

@kukkok3
Copy link
Contributor

@kukkok3 kukkok3 commented Dec 21, 2023

Description

Adding a UNIT_TEST UDC . This UDC will run unit tests and produce code coverage info using LLVM instrumentation-based coverage with the help of cargo-llvm-cov that supports nextest. The code coverage info will be printed on the stout after the test results as a support for the devs and will be also saved as an artifact to be used in CI.
Nextest will also create a test report in junit format that can be saved as artifact and used in CI.
The unit test alias and the testci alias have been removed as they will be substitute with a earthly target

Related Issue(s)

List the issue numbers related to this pull request.

e.g., Closes #123, Resolves #456 Fixes #367

Please confirm the following checks

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream module

@kukkok3 kukkok3 self-assigned this Dec 21, 2023
@kukkok3 kukkok3 marked this pull request as ready for review December 22, 2023 09:55
@kukkok3 kukkok3 requested review from jmgilman and stevenj December 22, 2023 09:55
@kukkok3 kukkok3 changed the title feat: UNIT_TEST UDC target feat: UNIT_TEST UDC Dec 22, 2023
@minikin
Copy link
Collaborator

minikin commented Dec 27, 2023

@kukkok3 lgtm. Feel free to merge.

@kukkok3 kukkok3 merged commit 2cd566a into master Dec 27, 2023
@kukkok3 kukkok3 deleted the feat-test-coverage branch December 27, 2023 14:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants