* Install jest
* Configure jest script
* Fix eslintrc
* Add @types/jest
* Add test for validate-new-version
* Fix eslintrc
* Add workflow file
* Add node version
* cd to script/release
* Fix workflow file
* Fix version
* Ignore from root
* Update yarn.lock
* Set defaults.run.working-directory
* Disable Jest's default transform (Babel)
https://jestjs.io/docs/en/next/code-transformation#defaults
Otherwise, I sometimes get this error because Babel tries to resolve Browserslist:
----
● plugin search should not crash when prettier isn't inside a directory › encountered a declaration exception
ENOENT: no such file or directory, stat '/mnt/d/dev/prettier/tests_integration/mnt/d/dev/prettier/tests_integration/runPrettier.js'
52 | jest.spyOn(fs, "statSync").mockImplementation((filename) => {
53 | if (path.basename(filename) === "virtualDirectory") {
> 54 | return origStatSync(path.join(__dirname, __filename));
| ^
55 | }
56 | return origStatSync(filename);
57 | });
at Object.<anonymous> (tests_integration/runPrettier.js:54:14)
at isFile (node_modules/browserslist/node.js:38:42)
at eachParent (node_modules/browserslist/node.js:46:13)
at Object.getStat (node_modules/browserslist/node.js:197:15)
at browserslist (node_modules/browserslist/index.js:433:19)
at resolveTargets (node_modules/@babel/helper-compilation-targets/lib/index.js:174:46)
----
* Followup work on setup github actions
* Coverage report & split `prod_lint`
* Add env
* Remove coverage report on azure pipelines
* Remove build step on lint
* remove coverage report on prod_test
* Use `ci-info` instead of `is-ci`
* Always enable `ENABLE_TEST_RESULTS` and `AST_COMPARE` on CI
* Standalone test and remove some env
* coverage report
* reduce matrix
* standalone test
* `ci-info`
* Remove token
* Disable `coverage` on azure pipelines
* use master version of codecov-action
* Link to master status
* fix prod lint
* Use boolean env
* Remove locv report
* Try lcov report
* pin `codecov-action` version, enable `verbose`
* azure coverage
* Name
* Trigger CI
* Use `basename`
* Trigger CI
* Try `runInBand`
* try `maxWorkers`
* Remove azure pipelines
* clean up
Co-authored-by: Georgii Dolzhykov <thorn.mailbox@gmail.com>
* Followup work on setup github actions
* Coverage report & split `prod_lint`
* Add env
* Remove coverage report on azure pipelines
* Remove build step on lint
* remove coverage report on prod_test
* Use `ci-info` instead of `is-ci`
* Always enable `ENABLE_TEST_RESULTS` and `AST_COMPARE` on CI
* Standalone test and remove some env
* coverage report
* reduce matrix
* standalone test
* `ci-info`
* Remove token
* Disable `coverage` on azure pipelines
* use master version of codecov-action
* Link to master status
* fix prod lint
* Use boolean env
* Remove locv report
* Try lcov report
* pin `codecov-action` version, enable `verbose`
* azure coverage
* Name
* Trigger CI
* Use `basename`
* Trigger CI
* Try `runInBand`
* try `maxWorkers`
Co-authored-by: Georgii Dolzhykov <thorn.mailbox@gmail.com>
- upload coverage report (codecov) from azure pipelines
- only build `dist` once (`dist` is now shared between production jobs)
- run production tests on macOS (not sure why but it's faster than others)
- extract shareable steps
- remove travis/circle
* Add azure pipelines
* Add gitattributes
* Updating tests to work on Windows or Unix
* Lint
* Cleaning up
* Fixing names
* Clean up naming
* try to consolidate images
* Clean up
* Add back txt to gitattributes
* Report test summaries to CircleCI
* Don’t run jest-junit on Node <6
(it uses default function parameters)
* Address @lydell’s comment
* Use @duailibe’s suggestion
* 🔥 `jest-junit` key in production package.json
* Move config to jest.config.js
* chore: upgrade Jest
* chore: update snapshots
* chore: lock down babel dependency using invalid syntax
* 2 args to test.skip
* use jest 22 for now
* Revert "2 args to test.skip"
This reverts commit 691fdc3f99e320f2303958f2b503f7b4c93fa455.
* remove snapshot name from matcher
* fix standalone tests skips
* Automatically load plugins from package.json
* Fix build by adding json extension
* Fixup misuse of options argument
* Rewire graceful-fs to fs
* Document graceful-fs issue
* Alias graceful-fs to fs in Rollup
* Make production tests always run against dist/
* Try to mock process.stdin instead of get-stream
* fix: mock `get-stream` from `index.js`
* refactor: remove unnecessary variable
* Try `transform: {}` in jest.config.js
* Add comment explaining the unusual get-stream mocking
fisker Cheung