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
* convert mocha tests to jest
* jest 23
* add jest configs
* use material css
* fix windows
* forceExit jest test
* force exit eject
* test
* test
* retrigger test
* remove appveyor comment
* try to remove pretendToBeVisual option
* use jsdom env
* test environment
* no cache
* test no close
* bring back raf
* test revert all broken changes
* add back jsdom
* remove jsdom
* node test environment
* use latest change
* runInBand
* runInBand
* comment test run
* try different jest option
* standardize jest test options
* increase heap size
* remove heap size config
* support scoped packages for cra --scripts-version option
* upgrade jest version
* fix windows
* fix windows again
* jest 23.4.1
* babel-jest
* babel-jest
* split out kitchhensink
* travis node 6
* travis node 6 config
* node 6 travis eject
* cache yarn
* only cache yarn
* remove unrelated changes
* typo
Copy file name to clipboardexpand all lines: fixtures/kitchensink/README.md
-1
Original file line number
Diff line number
Diff line change
@@ -51,4 +51,3 @@ An usual flow for the test itself is something similar to:
51
51
52
52
- since `initDOM` returns a `Document` element, the previous `id` attribute is used to target the feature's DOM and `expect` accordingly
53
53
54
-
These tests are run by **mocha** (why not **jest**? See [this issue](https://github.com/facebook/jest/issues/2288)) and the environments used are both `development` and `production`.
0 commit comments