Selective test on workspace name with the --package option

[cristiano-belloni]

Enhance modular test with the following behaviour:

$ modular test --package PACKAGE_NAME
# Run all tests for PACKAGE_NAME

$ modular test --package PACKAGE_NAME_1 --package PACKAGE_NAME_2
# Run all tests for PACKAGE_NAME_1 and PACKAGE_NAME_2

$ modular test --package PACKAGE_NAME --ancestors
# Run all tests for PACKAGE_NAME and all other workspaces that, directly or indirectly, depend on it

$ modular test --package PACKAGE_NAME --changed
# Options are not compatible: exit with error

modular test SOME_REGEX --package PACKAGE_NAME
# Options are not compatible: exit with error

[changeset-bot]

🦋 Changeset detected

Latest commit: 0111c22

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
modular-scripts	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coveralls]

Coverage decreased (-0.2%) to 33.195% when pulling 0111c22 on feature/single-package-test into deaee2c on main.

[sgb-io]

Also a typo?

Suggested change

	repeated to select more than one workspace. Can be combined with the
	repeated to select more than one package. Can be combined with the

[sgb-io]

Maybe not. I'm confused - are they workspaces or packages? In my mind, a workspace can consist of many packages (the workspace usually means the packages dir, if talking in yarn languge)

[cristiano-belloni]

It's incredibly confusing, but it seems that any package that falls in the workspaces glob / array in the manifest is called a "workspace": https://classic.yarnpkg.com/lang/en/docs/workspaces/

[sgb-io]

nit: could maybe use a single expect statement here

[cristiano-belloni]

Mmmh, not sure what you mean - it's not possible to pass an array to toContain and it's not possible to chain expectations, how would you use a single expect?

[cristiano-belloni]

Unless you're saying that we can conflate packages/c/src/__tests__/utils/c-nested.test.ts and packages/c/src/__tests__/utils/c-nested.test.ts into their common root: packages/c/src/__tests__/; in that case I explicitly wanted to show that we're executing all the tests of a workspace, including those in subdirectories.

[sgb-io]

What's the shape of resultPackagesWithAncestors.stderr? I can imagine we can find a way to dedupe this a bit, but it's really not a big deal