-
Hey :)
jest-styled-components is very handy but for different components sometimes require different testing strategies.
What about allowing optional options per test to:
- [x] generate snaps…
-
### Self-service
- [ ] I'd be willing to implement a fix
### Describe the bug
Package names seem to be unnecessarily truncated when using `yarn upgrade-interactive` on a narrow terminal — for examp…
-
Here is my package.json
{
"name": "jest-integration-example",
"scripts": {
"test": "jest",
"fuzz": "JAZZER_FUZZ=1 jest",
"coverage": "jest --coverage"
},
"devDependencies": {
"@…
-
Apologies if this repo is not the right place to post, I wasn't quite sure to post this under ttypescript, or to have it under ts-jest.
I have an issue in where I am seeing many warnings upon runni…
-
Jest has the option, to save the snapshot "inline" within the test code file.
Have a look at https://jestjs.io/docs/en/snapshot-testing#inline-snapshots
-
### Verify canary release
- [X] I verified that the issue exists in the latest Next.js canary release
### Provide environment information
Operating System:
Platform: win32
Arch: x…
-
As this project matures and we're publishing regular releases to the public App and Play Stores, we need to begin working toward as much test coverage as possible, and we will integrate it into our ex…
-
Something like
```javascript
expect: throws: x();
```
would be nice to avoid wrapping the call in a function like assertion libraries usually require:
```javascript
expect(() => x()).toThrowErro…
-
Currently some tests take a bit too long to run. Here is a sample run on my dev laptop:
```
...
$ jest
PASS src/test/feature-map.spec.ts (34.231 s)
PASS src/test/feature-dns.spec.ts (28.953 s…
-
**Summary**
This is a fix for this issue
When running a single test that has many test cases the error messages are printed before the list of failing/passing tests which makes us to scroll up e…