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
{{ message }}
Repository navigation
Commit cf1b834
Browse filesBrowse the repository at this point in the historyBrowse files
-`minify-corpora.spectest.js` — `yarn test:minify-corpora`, in three [parts](#splitting-one-file-across-workers) its corpus groups are dealt to by `minify-corpora-timings.json`; the last part to finish checks no table entry went unmet
121
+
-`minify-corpora.spectest.js` — `yarn test:minify-corpora`; CI runs it in three [parts](#splitting-one-file-across-workers), each minifying the sources whose name hashes to it, and the last part to finish checks no table entry went unmet
122
122
-`js-fuzz.spectest.js` — `yarn test:js-fuzz`: programs from `test/helpers/jsFuzzProgram.js`, in the sloppy ES5 terser's ufuzz writes, in modern syntax, as modules importing a fixed `dep` and as webpack-shaped bundles, minified under ufuzz's option sets, webpack's and random ones; the parser is held to acorn's tree on each program and output, the printer to the tree it read and to its own output, each output to what its program prints and exports, the default set's source map to its output and source, and the output to what it prints minified again. Needs no submodule; `JS_FUZZ_SEED=<n>` replays one seed, `JS_FUZZ_SEED=random` runs a new one named in the test's title, and `JS_FUZZ_PROGRAMS` sets the programs per seed.
123
123
124
124
### `statsCases/`
@@ -197,7 +197,7 @@ During the test run, webpack compiles this project and compares the result with
197
197
198
198
### Splitting one file across workers
199
199
200
-
Jest runs each file in one worker, so a long suite in one file leaves the runner's other cores idle. `--parts=<n>` (read by `jest.config.js`) runs every matched file in `n` workers at once, as `n` projects whose coverage merges as usual; global setup and teardown run once. A file splits its own work with `test/helpers/testParts.js`: `keysOfPart(keys, weights)`returns the keys this part runs, dealt by measured weight so the parts end together, and `currentPart()` returns `[part, parts]`, e.g. to run a check once in part 1. Without the flag a file is one part and runs everything; a file that doesn't use the helper runs whole in every part, so pass the flag only to a script that runs a file using it.
200
+
Jest runs each file in one worker, so a long suite in one file leaves the runner's other cores idle. `--parts=<n>` (read by `jest.config.js`) runs every matched file in `n` workers at once, as `n` projects whose coverage merges as usual; global setup and teardown run once. A file splits its own work with `test/helpers/testParts.js`: `isInPart(key)`tells whether this part runs the work named `key`, by a hash of the name, so nothing to measure or store, and `currentPart()` returns `[part, parts]`, e.g. to run a check once in part 1. Without the flag a file is one part and runs everything; a file that doesn't use the helper runs whole in every part, so pass the flag only where it runs a file using it — e.g. CI's `yarn cover:minify --parts=3`.
0 commit comments