Add support for the yarn test -f [externalPackage] command

[ma2ciek]

A follow-up to the environment unification. I feel we should add support for yarn test -f [externalPackage] when the externalPackage is cloned to the external directory.

cc @pomek

---

If you'd like to see this feature implemented, add a 👍 reaction to this post.

[pomek]

It works when you specify a package name. However, (I guess) the ticket is about supporting an option to test all packages inside an external repository.

For the following tree:

packages/
    ...
    ckeditor5-xyz
external/
    custom-repository/
        packages/
            ckeditor5-foo/
            ckeditor5-bar/

The following command:

yarn run test -f custom-repository

Should be translated to:

yarn run test -f foo,bar

At this point, I would like to rename the requested option name: --repository or as an alias -r which, if specified, reads all directories inside the packages/ directory and passes it as additional values for the --files option.

So, if you would like to execute all custom-repository packages and xyz, you could type:

yarn run test -f xyz -r custom-repository

And it will be resolved as:

yarn run test -f xyz,foo,bar

[ma2ciek]

This is a part I certainly don’t want to overcomplicate by introducing new resolution semantics etc. I like your proposal, on the other hand, the implementation becomes pretty ugly with our strategy of stripping the ckeditor5-  part whenever possible 😄

Maybe we could use -e instead of -r as a shortcut from --external? On the other hand, we could enhance the -r option to support yarn test -r ckeditor5 as well (IDK if this makes sense).

[pomek]

we could enhance the -r option to support yarn test -r ckeditor5 as well (IDK if this makes sense).

I was thinking about it as well and it makes sense to have an option to test all packages from the root directory without removing external stuff.

[mlewand]

An option to run tests per repository seems to be fine 👍