-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Docs: verbose's default is "true" and not "false" #9205
Comments
The verbose reporter is the default if there's only |
Could point it out in the docs |
Fair point. @thernstig would you feel like contributing this bit? |
There are two tests running, like this: // beverage.test.js
const myBeverage = {
delicious: true,
sour: false,
};
describe('my beverage', () => {
it('is delicious', () => {
expect(myBeverage.delicious).toBeTruthy();
});
it('is not sour', () => {
expect(myBeverage.sour).toBeFalsy();
});
}); Result ~/test (jest)> jest
PASS server/config.unit.test.js
my beverage
✓ is delicious (1ms)
✓ is not sour (1ms)
Test Suites: 1 passed, 1 total
Tests: 2 passed, 2 total
Snapshots: 0 total
Time: 0.528s
Ran all test suites. edit: Did you mean just one test suite |
By a "one test" I mean "one file with test cases" or "one test suite". If you add another file, it will be gone |
@thymikee Yes, edited my last comment suspecting this was the case. I have verified you are correct. Maybe a small doc update would highlight this, let me see if I can get time to send a MR soon. |
Appreciate the great support and issue tracking from both of you :) |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
🐛 Bug Report
When there is no 'verbose' property defined in jest.config.js, it defaults to
true
and notfalse
as per https://jestjs.io/docs/en/configuration#verbose-booleanTo Reproduce
Add this code to a project and place a test in the server/ directory:
Expected behavior
The test case names should not be displayed in the console.
envinfo
The text was updated successfully, but these errors were encountered: