-
Our project has been using CRA 3.4.0 and when we run `react-scripts test --env=jsdom` it has used the setupTests.js file, which has in it these lines:
```
const jasmineReporters = require('jasmine-r…
-
A test failed on a tracked branch
```
Error: expect(element).toHaveTextContent()
Expected element to have text content:
yesterday
Received:
Last alert23 hours ago
at Object.toHaveTextContent…
-
### Details
Currently, when adopting the native test runner, it is very hard to understand how to mock standalone functions used in the unit under test. Judging by [this SO question](https://stacko…
-
A test failed on a tracked branch
```
Error: thrown: "Exceeded timeout of 5000 ms for a test.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jes…
-
I cloned `https://github.com/pelotom/runtypes`, deleted the `yarn.lock`, ran `npm i` and then `npm-why ws`.
```
➜ runtypes git:(master) ✗ npm-why ws
(node:47582) UnhandledPromiseRejectionWarning…
-
A test failed on a tracked branch
```
Error: thrown: "Exceeded timeout of 5000 ms for a test.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jes…
-
As an observer it seems it would be doable (and beneficial) to allow users to run the storybook tests directly through Jest. My thinking is you can expose a jest preset that configures jest to search …
-
**Summary**
When running a fresh clone of the repository on the master branch it seems as if the ChildProcessProxy test for `should throw an OutOfMemoryError if the process went out-of-memory:` fai…
-
It looks like fake timers have been purposefully turned off. Would it be possible to implement fake timers?
-
### Describe the bug
```session
$ npx run test-storybook
● Test suite failed to run
Cannot find module '@babel/preset-typescript'
Require stack:
- /project/node_modules/@babel/…