Deprecate old test script commands

[rickhanlonii]

Overview

These aliases have been replaced with the easier to use arguments like --debug and --prod and the aliases have been proxing to the new commands for awhile now.

Deprecating the aliases now to give people a chance to use the new commands directly before removing them later.

[rickhanlonii]

In the end we'll have three base test commands:

• test
• test-www
• test-build-devtools

[rickhanlonii]

Well, we already only have three commands since the aliases proxy to them.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 5229225:

Sandbox	Source
React	Configuration

[gaearon]

Do we reference the old commands anywhere in the docs or PR template?

[sizebot]

No significant bundle size changes to report.

Size changes (stable)

Generated by 🚫 dangerJS against 5229225

[sizebot]

No significant bundle size changes to report.

Size changes (experimental)

Generated by 🚫 dangerJS against 5229225

[rickhanlonii]

@gaearon good thinking, updated the reference in this repo and I'll follow up with the changes to the website here.

[sebmarkbage]

Please update the CI command names. They should represent the command you have to run to repro the test failure. Although not sure how you’d tell someone to put a double dash.

[sebmarkbage]

Tbh this is a lot less discoverable (if we actually remove them). I always go to package JSON files in projects to find all the commands I might need to run.

Where is a single list of commands I need to run now?

[rickhanlonii]

Note that the only thing that's really changing between the aliases and the new commands is that --debug, --prod, --build and --variant are now options for each command instead of listing a subset of all permutations of the commands.

So instead of test, test-build, test-prod, and test-build-prod it's test [--build] [--prod]. The goal is to makes it easier to do what you want without searching through the aliases to find the right command. If you want to run the prod tests you add --prod, if you want to run the tests against the build, you add --build.

This also means you can easily test missing permutations. For example, we don't have a debug-test-prod-build.

For a list of all supported options, we have the help message:

Does this help @sebmarkbage?

[rickhanlonii]

Update: I added test-stable and test-www-classic so we now have a test script per release channel:

• yarn test (experimental)
• yarn test-stable (stable)
• yarn test-www (www-modern)
• yarn test-classic (www-classic)

I've also updated the circle test names to reflect the command that you would run to repro. I think we should give this a try and if we hate it we can re-evaluate.