## Bug
- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Errors have helpful link attached, see `contributing.md`
## Feature
- [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Documentation added
- [ ] Telemetry added. In case of a feature if it's used or not.
- [ ] Errors have helpful link attached, see `contributing.md`
## Documentation / Examples
- [ ] Make sure the linting passes by running `yarn lint`
This ensures we trim test output that will exceed the amount that can be shown in GitHub actions so that we can still see which tests failed instead of un-helpful test logs.
* Move unit tests to one folder
* Migrate unit tests to TypeScript
* add test types to lint
* Ensure ts(x) tests are run with util
* Add tsx extension to jest config
* bump
* Update polling env var for tests in CI
* Update polling value
* always use polling
* Revert "always use polling"
This reverts commit 281875de921874592a6755d67acaad7441c06e22.
* test disabling tcp/udp offloading
* fix quotes
This updates to only output a test's logs when it fails to reduce the noise in the CI's logs to allow easier investigating a failure. This also updates azure to leverage the `run-tests` script when testing ie11 to allow retrying similar to our other tests.
This PR upgrades `jest-worker` and `jest-cli` to the latest pre-release version, also removed `jest-circus` which is included in Jest by default. `jest-worker@next` includes a fix for memory leak that we need (https://github.com/facebook/jest/pull/11187).
Fixes#22925. This will also improve the OOM issue for `next dev` #15855.
jest retries seem to be masking test failures, like the `auto-export` one (and maybe others). I turned it off for now. The `auto-export` test fails when retries are turned off.
the output of this test failure was a bit unhelpful so I also improved it.
Many tests have anonymous page functions.
- Reduce jest retries to 2 for a total of 3 attempts
- Disable retries in `invalid-href` test. I noticed jest retries don't help when this test fails (see log output of https://github.com/vercel/next.js/runs/904147534).
* Add initial config
* Comment out other action
* Update config
* Update config
* Update configs
* rename requires -> needs
* Update configs
* Update configs
* Enable headless mode
* Disable circleci while testing
* Disable build-test-deploy in circle
* Update build step
* Disable fail fast
* Update configs
* Add runs-on to publish steps
* bump
* Update config
* Update group count
* Update checkout path
* Update test all concurrency
* Handle EPIPE errors
* Revert "Handle EPIPE errors"
This reverts commit a993565bbdd77df136e07d54eb83ed32b18e5963.
* Update test to handle EPIPE in test
* Remove CircleCi config
* Revert "Update test to handle EPIPE in test"
This reverts commit c8cb72d5303b5fd165016f9eba6c8c888d8a1907.
* Update to use node 10 and see if EPIPE error is still present
* Revert "Revert "Update test to handle EPIPE in test""
This reverts commit efd2abe7c35c12bf78530064796d853c171efcf1.
* Revert "Update to use node 10 and see if EPIPE error is still present"
This reverts commit 893da4f31279228ebec6fa208c34ef179a6ebaf4.
* Add todo for node issue
* undo lint change as it should be correct
* Add dummy step to require
* Add runs-on for dummy job
* Add splitting by timings for Azure
* Add --timings flag for azure
* Update timings API
* Update timings var
* Fix test directory not being reset before re-trying
* Update to re-use CircleCI timing data
* Bump concurrency for Azure
* Remove extra logging
* Update timeout for create-next-app tests
Co-authored-by: Joe Haddad <timer150@gmail.com>
* Add warning for getStaticParams without getStaticProps
* Throw error instead of logging to make sure it's noticed
* Lower default concurrency for tests
* Tweak test set-up
* Update azure config
* Add cleaning test files and windows handling
* Limit windows test to one at a time
* Tweak test settings
* Update tests splitting
* remove custom concurrency for azure
* Test Azure var
* Update Azure config
* bump
* Simplify cleaning up