Allow --list-projects in new dotnet test experience

[Youssef1313]

This is a feature request to allow --list-projects when running the new dotnet test experience on a solution. It makes users more confident that their setup is correct and that all intended test projects are correctly considered.

FYI @mariam-abdulla

[Youssef1313]

This is an idea that came to mind, but I'm not sure how much value it is. We may need to discuss and/or wait for user feedback.

[nohwnd]

My suggestion is to keep this under --list-tests, we already show the projects there, we could add a list of projects + test counts to the end, which would be the functionality.

it could also be an option for --list-tests, e.g. --list-tests --output minimal

[Youssef1313]

--list-tests --output minimal

We already have --output command line option. It may be confusing if we use that for two different purposes. Also, I think listing the projects will be a feature of SDK, while list-tests is a feature of MTP. --output is also an option of MTP. My understanding is that options that are recognized by SDK will not be passed down to MTP as well, and I'd try to avoid special casing that for specific options.

[nohwnd]

Okay so not --output, but I would still keep this as part of --list-tests. This is already understood by dotnet test, and you probably want to do full discovery to make sure stuff works.

[Youssef1313]

@nohwnd --list-tests is not understood by dotnet test for the new experience AFAIK. It's currently just passed down to the test executable.

and you probably want to do full discovery to make sure stuff works.

For the purpose of listing only the projects, why would I do the full discovery?

[mariam-abdulla]

This is a feature request to allow --list-projects when running the new dotnet test experience on a solution. It makes users more confident that their setup is correct and that all intended test projects are correctly considered.

FYI @mariam-abdulla

We are passing --list-tests as an unrecognized token (because the test application does the work), we do check for its existence in dotnet sdk because the UX needs that.
I find Youssef's idea good, but let's wait for feedback from the users.

[nohwnd]

This is the current experience, to me it is 90% there.

[Evangelink]

Although I like the idea to show test assemblies, I think it fits better with having ways to change format of --list-tests. Couple of related requests: #3527, #3221