@@ -11,7 +11,6 @@ Especially useful for having mock projects, built with specific bundlers and run
11
11
12
12
<!-- #toc -->
13
13
- [ Run all the tests] ( #run-all-the-tests )
14
- - [ Run all the tests with all the logs] ( #run-all-the-tests-with-all-the-logs )
15
14
- [ Debug a test] ( #debug-a-test )
16
15
- [ Test a plugin] ( #test-a-plugin )
17
16
- [ Bootstrapping your test] ( #bootstrapping-your-test )
@@ -26,22 +25,14 @@ Especially useful for having mock projects, built with specific bundlers and run
26
25
yarn test
27
26
```
28
27
29
- ## Run all the tests with all the logs
30
-
31
- By default, jest is in silent mode and won't show any logs.
32
-
33
- ``` bash
34
- yarn test:noisy
35
- ```
36
-
37
28
## Debug a test
38
29
39
30
You can target a single file the same as if you were using Jest's CLI.
40
31
41
32
Within your test you can then use ` .only ` or ` .skip ` to target a single test in particular.
42
33
43
34
``` bash
44
- yarn test:noisy packages/tests/...
35
+ yarn test packages/tests/...
45
36
```
46
37
47
38
## Test a plugin
@@ -98,19 +89,19 @@ During development, you may want to target a specific bundler, to reduce noise f
98
89
For this, you can use the ` --bundlers=<name>,<name> ` flag when running your tests:
99
90
100
91
``` bash
101
- yarn test:noisy packages/tests/... --bundlers=webpack4,esbuild
92
+ yarn test packages/tests/... --bundlers=webpack4,esbuild
102
93
```
103
94
104
95
If you want to keep the built files for debugging purpose, you can use the ` --cleanup=0 ` parameter:
105
96
106
97
``` bash
107
- yarn test:noisy packages/tests/... --cleanup=0
98
+ yarn test packages/tests/... --cleanup=0
108
99
```
109
100
110
101
If you want to also build the bundlers you're targeting, you can use the ` --build=1 ` parameter:
111
102
112
103
``` bash
113
- yarn test:noisy packages/tests/... --build=1
104
+ yarn test packages/tests/... --build=1
114
105
```
115
106
116
107
### More complex projects
0 commit comments