You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ideally I'd have a 100% flow coverage in my projects. However, this is usually not realistic, there are almost always parts of the code base that either can't be covered at all, or are extremely difficult to cover properly. As a result, we generally can't set the threshold to 100% for CI builds, we need to lower it to a somewhat arbitrary lower value. This has as the unintended side-effect that the build will now allow a non-zero percentage of unintended uncovered code as well.
It would therefore be very useful if we could somehow specify that certain parts of the code should not count towards coverage percentage, e.g. by using comments. For example:
Ideally I'd have a 100% flow coverage in my projects. However, this is usually not realistic, there are almost always parts of the code base that either can't be covered at all, or are extremely difficult to cover properly. As a result, we generally can't set the threshold to 100% for CI builds, we need to lower it to a somewhat arbitrary lower value. This has as the unintended side-effect that the build will now allow a non-zero percentage of unintended uncovered code as well.
It would therefore be very useful if we could somehow specify that certain parts of the code should not count towards coverage percentage, e.g. by using comments. For example:
The tool could still warn about missing coverage, but it just wouldn't count towards to threshold.
With something like this we would be able to set the threshold as 100% and explicitly opt-out of coverage where desired.
Would something like this be possible and desirable for this project?
The text was updated successfully, but these errors were encountered: