Support multiple test projects in a solution/workspace.
See original GitHub issueI really appreciate this extension but it would be even more useful if it supported multiple test projects per solution/workspace in settings.json like:
{
"dotnet-test-explorer.testProjectPaths": ["path/to/some/test/proj", "path/to/other/test/proj"]
}
Issue Analytics
- State:
- Created 6 years ago
- Reactions:28
- Comments:37 (1 by maintainers)
Top Results From Across the Web
Multi-root Workspaces in Visual Studio Code
You can work with multiple project folders in Visual Studio Code with multi-root workspaces. This can be helpful when you are working on...
Read more >Managing multiple projects and their dependencies
Manage related projects in one place using a workspace, or configure build-time dependencies between different Xcode projects using cross-project references.
Read more >Multi-repo Support in Visual Studio - Microsoft Developer Blogs
In this blog learn about the new support for using multi-repos. ... Open solution with projects in different repositories.
Read more >Solved: Project Workspace - view multiple projects - ServiceNow
Solved: Hello! In the Project Workspace, under the "Planning" tab, we're able to see that project's PRJTASKs in a Gantt view, which is....
Read more >Xcode 5: Multiple test targets in one scheme - Stack Overflow
In Xcode 5, I have a workspace with multiple projects and a scheme that should run all the test targets of the various...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This should be fixed with the v05 update. Please open new issues if something is not working as expected. Thanks for your patience 🌈
@stefanforsberg You are correct.
It’s probably best to approach the multiple test project scenario first and then approach the workspace (multiple solution project) issue as a separate feature. I would guess that the monolith issue would both block and feed into the bigger workspace issue.
We often have several solution projects per-workspace, each with several test-projects. We dynamically generate the workspace via CLI for faceted views of a much larger set of microservices. 😃