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
My understanding of the skip vs todo vs failing API was:
test.skip([title], fn) - A test function is provided, but it is skipped(i.e. fn is never called). Common use: removing a failing test while you are in the middle of refactoring. People probably shouldn't be checking test.skip tests into their master branch (especially once test.failing is implemented). Title is optional, just like the normal test method.
test.todo(title) - No test function is allowed, but a title is required. Common use: documenting future tests (and maybe features) that need to be written.
test.failing([title], fn) - Proposed in A way to submit tests that should fail. #673- Optional title, test function is required and will be run (but is expected to fail). Common use: allow users to create PR's that reproduce the problem. Reporting bugs in a way that does not break the build.
Issue:
Right now the API for 2 is more like: test.todo(title, [fn]) - title is required, but fn is optional (and ignored).
The text was updated successfully, but these errors were encountered:
Overview:
My understanding of the
skip
vstodo
vsfailing
API was:test.skip([title], fn)
- A test function is provided, but it is skipped(i.e.fn
is never called). Common use: removing a failing test while you are in the middle of refactoring. People probably shouldn't be checkingtest.skip
tests into their master branch (especially oncetest.failing
is implemented). Title is optional, just like the normaltest
method.test.todo(title)
- No test function is allowed, but a title is required. Common use: documenting future tests (and maybe features) that need to be written.test.failing([title], fn)
- Proposed in A way to submit tests that should fail. #673- Optional title, test function is required and will be run (but is expected to fail). Common use: allow users to create PR's that reproduce the problem. Reporting bugs in a way that does not break the build.Issue:
Right now the API for
2
is more like:test.todo(title, [fn])
-title
is required, butfn
is optional (and ignored).The text was updated successfully, but these errors were encountered: