Add check to make sure one or more tests have run before notifying #6495
Conversation
Codecov Report
@@ Coverage Diff @@
## master #6495 +/- ##
==========================================
+ Coverage 63.48% 63.48% +<.01%
==========================================
Files 227 227
Lines 8697 8698 +1
Branches 3 4 +1
==========================================
+ Hits 5521 5522 +1
Misses 3175 3175
Partials 1 1
Continue to review full report at Codecov.
|
| Object { | ||
| "message": "3 tests passed", | ||
| "title": "100% Passed", | ||
| }, |
There was a problem hiding this comment.
Should there be some snapshots added?
There was a problem hiding this comment.
My understanding is that this is a result of the firstRun: i === 0 logic which is causing new snapshots in the the change testMode scenarios, due to me adding a new aggregation result to the notifyEvents array, so I believe this is expected?
|
an explicit test with zero tests (with |
|
I've added an explicit test which runs are part of each aggregation result scenario with the above. Let me know what you think! |
This Pull Request updates dependency [jest](https://github.com/facebook/jest) from `v23.1.0` to `v23.2.0` <details> <summary>Release Notes</summary> ### [`v23.2.0`](https://github.com/facebook/jest/blob/master/CHANGELOG.md#​2320) [Compare Source](jestjs/jest@v23.1.0...v23.2.0) ##### Features - `[jest-each]` Add support for keyPaths in test titles ([#​6457](`jestjs/jest#6457)) - `[jest-cli]` Add `jest --init` option that generates a basic configuration file with a short description for each option ([#​6442](`jestjs/jest#6442)) - `[jest.retryTimes]` Add `jest.retryTimes()` option that allows failed tests to be retried n-times when using jest-circus. ([#​6498](`jestjs/jest#6498)) ##### Fixes - `[jest-cli]` Add check to make sure one or more tests have run before notifying when using `--notify` ([#​6495](`jestjs/jest#6495)) - `[jest-cli]` Pass `globalConfig` as a parameter to `globalSetup` and `globalTeardown` functions ([#​6486](`jestjs/jest#6486)) - `[jest-config]` Add missing options to the `defaults` object ([#​6428](`jestjs/jest#6428)) - `[expect]` Using symbolic property names in arrays no longer causes the `toEqual` matcher to fail ([#​6391](`jestjs/jest#6391)) - `[expect]` `toEqual` no longer tries to compare non-enumerable symbolic properties, to be consistent with non-symbolic properties. ([#​6398](`jestjs/jest#6398)) - `[jest-util]` `console.timeEnd` now properly log elapsed time in milliseconds. ([#​6456](`jestjs/jest#6456)) - `[jest-mock]` Fix `MockNativeMethods` access in react-native `jest.mock()` ([#​6505](`jestjs/jest#6505)) ##### Chore & Maintenance - `[docs]` Add jest-each docs for 1 dimensional arrays ([#​6444](`jestjs/jest#6444)) --- </details> --- This PR has been generated by [Renovate Bot](https://renovatebot.com).
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
As raised in #6363, when running
jest-cliwith the--notify --watchoptions, a notification would pop up even if no tests had run. This PR adds a check to make sure one or more tests have run before notifying the user.Test plan
I've added a new scenario where no tests exist in the suite and updated the relevant snapshots to match the new expected output.