rsnext/test
Tim Neutkens cae7833af4
Ensure Turbopack passing test list is sorted (#55948)
I noticed that running the script to pull in the results wasn't
deterministic between test runs, this ensures the list, passing,
pending, and errors are all sorted, which makes the diff only include
what actually changed between runs.

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->
2023-09-25 12:59:26 +02:00
..
.stats-app chore(ci): bump pnpm v8.6.11 to v8.7.1 (#54873) 2023-09-06 00:39:44 +00:00
__mocks__ [edge] bump @edge-runtime/* package suite (#49092) 2023-05-31 08:03:20 +00:00
development Loose types of app routes return value (#55849) 2023-09-25 11:34:21 +02:00
e2e Loose types of app routes return value (#55849) 2023-09-25 11:34:21 +02:00
examples feat(cli): introduce --tailwind flag (#46927) 2023-03-16 16:06:27 +01:00
integration Move client-navigation test to test/development (#55888) 2023-09-24 11:38:53 +02:00
lib test(turbopack): explicitly clean up instance for turbopack (#55772) 2023-09-21 23:50:13 +00:00
production test(integration): fix --turbo tests fixture setup (#55293) 2023-09-18 17:46:07 +00:00
unit Warn experimental.appDir option can be removed (#55346) 2023-09-13 23:38:17 +00:00
.gitignore ci(workflow): enable test trace upload (#51107) 2023-06-12 17:14:13 +00:00
build-turbopack-tests-manifest.js Ensure Turbopack passing test list is sorted (#55948) 2023-09-25 12:59:26 +02:00
jest-setup-after-env.ts fix(next-swc): skips client/server only checks when running with Jest to unblock testing (#54891) 2023-09-04 13:53:41 +02:00
jest.d.ts refactor smooth scroll bailout logic in app navigations (#53186) 2023-07-27 14:39:51 +00:00
readme.md refactor: split up CONTRIBUTING.md (#40515) 2022-09-16 14:54:58 -07:00
test-file.txt
turbopack-tests-manifest.json Ensure Turbopack passing test list is sorted (#55948) 2023-09-25 12:59:26 +02:00

See Testing for more information on how you can run/write/debug tests for Next.js.