We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Specs like: it('should initalize with no errors'); cause spec-reporter to report a failure when a pending spec would be more appropriate.
it('should initalize with no errors');
The text was updated successfully, but these errors were encountered:
I can't reproduce the behaviour you describe... This kind of spec are reported (by default or jasmine spec reporter) as:
I have used the example spec (npm run example) to test it. Could you reproduce your issue with it?
npm run example
Sorry, something went wrong.
Disabled specs was incorrectly reported as failed #28
b77a8b6
I finally succeed to reproduce this issue by focusing a spec:
describe('suite', function() { fit('should be executed', function() { }); it('should be skipped', function() { }); });
Executed 1 of 2 specs SUCCESS (1 SKIPPED) in 0.042 secs.
So in v2.2.1, disabled specs are reported as skipped.
No branches or pull requests
Specs like:
it('should initalize with no errors');
cause spec-reporter to report a failure when a pending spec would be more appropriate.The text was updated successfully, but these errors were encountered: