-
Notifications
You must be signed in to change notification settings - Fork 10
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
introduce MUST, SHOULD, MAY to allow better reporting #110
Comments
I really like this idea!
|
May be this could be done with an options parameter in function itIs (arg = 'MUST', options) or multiple MAY depending on the complexity |
I think it would be best to require the level for itIs - it will require a bit of work behorehand, but will be more explicit from there on. And just to put it out there: maybe we should make 'MUST' and 'SHOULD' required by default, so you'd have to opt-in to skip them. It would end up something like this:
|
If the ID option is retained, if defined the ID shall be displayed explicitly in the test name I agree to require a level. For practical reason it may be better to keep the ID optional until the tests and spec are stabilised. Changes imply a review of the CI. The ID could be the link with the specification. |
@michielbdejong @ylebre @edwardsph
Each test SHOULD be specified as a MUST, SHOULD, MAY so as to know the specification level required. An html report could be generated with the results (report: work to be done)
I tested a quite easy solution around wrapping jest functions with an
itIs
function :itIs('MAY')
(this allow for further reporting)itIs()
The test would look like this :
The result for
SKIP_MAY=1 npm run jest conneg.test.ts -- --verbose
the use of verbose is not needed here but allow to display each test result when there is a default folder of tests.
The text was updated successfully, but these errors were encountered: