-
Notifications
You must be signed in to change notification settings - Fork 27
Description
background
As part of #975 we cleaned up most documented but not run checks, which we would like to generally avoid, as they indicate either incorrect documentation or faulty scenario implementations.
There are legitimate situations where a documented check is not run, mostly for certain scenario preparation steps that might need to do some cleanup, but usually don't. Currently, there is no clear way to identify and differentiate such checks.
We have the option of explicitly skipping a check (via check.skip()
). In test reports this is currently not reported in a way that is distinguishable from a "forgotten" check, but that can likely easily be changed: currently, checks that are not run and documented with a TODO
are rendered in yellow in reports (see screenshot)

proposal
- Call
check.skip()
on all documented checks in situations where they do not need to be run. - Render skipped checks in a recognizable way in test reports