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
I have 20 files with tests and each of those files has its describe() section and at least one it() section. In Angular when a new component is create a test file is created automatically with a single boiler plate test to check whether the component is creating successfully. Sometimes a team member may be enticed to comment a failing test so they can deliver the code and to keep the build green.
I would like to have an option in karma.config.js to fail/show error when there's a single test suite that has a describe() block but doesn't have any it() blocks. There's already a similar option failOnEmptyTestSuite but that one is if there are no tests at all so perhaps it could be extended to cover this case too or add another option.
Actual behaviour
It would skip the entire empty test suite
Environment Details
Karma version: 3.0.0
Jasmine: 2.99.1
Angular 6.1.1
Steps to reproduce the behaviour
Have a couple of test files with Jasmine tests in them.
Add another test file with only a describe() block and no it() blocks
The text was updated successfully, but these errors were encountered:
Expected behaviour
I have 20 files with tests and each of those files has its
describe()
section and at least oneit()
section. In Angular when a new component is create a test file is created automatically with a single boiler plate test to check whether the component is creating successfully. Sometimes a team member may be enticed to comment a failing test so they can deliver the code and to keep the build green.I would like to have an option in
karma.config.js
to fail/show error when there's a single test suite that has adescribe()
block but doesn't have anyit()
blocks. There's already a similar optionfailOnEmptyTestSuite
but that one is if there are no tests at all so perhaps it could be extended to cover this case too or add another option.Actual behaviour
It would skip the entire empty test suite
Environment Details
Steps to reproduce the behaviour
describe()
block and noit()
blocksThe text was updated successfully, but these errors were encountered: