action #115022
closed
coordination #154777: [saga][epic] Shareable os-autoinst and test distribution plugins
coordination #108527: [epic] os-autoinst wheels for scalable code reuse of helper functions and segmented test distributions
Complete unit test coverage (with coverage analysis) in os-autoinst/wheel-launcher
Added by okurz almost 2 years ago.
Updated over 1 year ago.
Category:
Feature requests
Description
Motivation¶
os-autoinst/wheel-launcher is a rather simple "perl project" so let's have full unit test coverage with coverage analysis to provide a good example and template for others to follow
Acceptance criteria¶
- AC1: os-autoinst/os-autoinst-wheel-launcher has a codecov badge showing 100%
Suggestions¶
- The main goal is to cover the logic in wheel code so only cover that but don't overdo it
- Optional: Think about a mocked testapi or using backend::null automatically
- Optional: Include style checks, perl tidy, etc.
Related issues
1 (1 open — 0 closed)
- Copied from action #115019: os-autoinst/wheel-boot which can be used to test os-autoinst/wheel-launcher size:M added
- Target version changed from future to Ready
- Status changed from New to Feedback
PR to create unit tests: https://github.com/os-autoinst/os-autoinst-wheel-launcher/pull/5
These tests are relying on heavy mocking. They can help to verify that the logic within the wheel code itself is correct. They cannot show whether the invoked test API functions would really behave as expected. For the sake of reaching 100 % code coverage it should be good enough now.
- Status changed from Feedback to Resolved
The PR has been merged. So we're at 100 % test coverage including badge.
- Status changed from Resolved to Feedback
Please also ensure that we stay at 100% in the future
Isn't setting the target to 100 % in codecov.yaml good enough?
- Status changed from Feedback to Resolved
Also available in: Atom
PDF