Arg/option to avoid tuist test <target> regenerating/downscoping the workspace created for tuist generate

Why is this needed?

I just recently updated from a very old version of Tuist (4.70.0 -> 4.200.5) and found a change in the behavior of the tuist test command. It appears that it will always scope down the project to the minimal target set, which makes sense in some instances, particularly when you’re working on a constrained set of targets. In my use case, I’ve got a modularized codebase with test targets per module, but I always work with a workspace generated for all modules. This behavior change leads to every time I (or more often my LLM) invokes tests from the CLI, Xcode pops a dialog requiring me to authorize reloading the workspace from disk and I lose my app target & scheme until I re-run tuist generate again.

Maybe I’m missing some option / argument or some other workflow that makes this possible, but I didn’t see one and I didn’t see an existing open issue covering this. I can always fall back to not using the tuist test command, but it was a nice shorthand for what I wanted to do.

Would it be possible to have a --no-generate flag that assumes the project is already generated with the correct targets & schemes? Or alternatively, have a --full or --all or --unscoped or something like that to indicate that the test command should still generate a project containing all targets, even if we only plan to run tests for a subset of them?

Thanks for the great tool!

Steps to address the need

We’d first need to land on an approach that’s acceptable to maintainers before defining/scoping the solution.