I have a solution with some test projects containing unit tests.
When I run all tests, I would like to execute one project at a time, i.e., all the unit tests of the first project, then all the unit tests of the second project, ecc.
Is it possible with Visual Studio 2010?
What you can do is set multiple startup projects. To do so:
In the Project menu, under Properties, expand Common Properties to select Startup Project. From here you can select Multiple Startup Projects, after which you will be capable of debugging more than one project at once.
Hopefully this helps you.
Related
I have a pretty simple question: What kind of project should I create for Integration Tests in Visual Studio? The only proposed project type under Test tab in Visual C# is Unit Test Project, but it's not integration test, so I'm not sure
This is what I read, but couldn't find an answer :
Integration Testing In Visual Studio With Different Project Types
How do you separate unit tests from integration tests in Visual Studio?
Thanks!
Use the unit test project template. You will create your integration tests in there.
The unit test project is just a template that provisions the necessary dependencies. You could just as easily create an empty project and manually add what it needed.
I have seen this:
Running two projects at once in Visual Studio
But I have another problem.
My solution had many executable projects.
Maybe I can allocate them into different groups.
For each group, It has a specific one or more startup projects.
So how can I configure it with Visual Studio 2017?
(Could I making some configuration in the project properties?)
You can use the SwitchStartupProject extension to select the startup project from a dropdown and switch between multi-project startup configurations.
When I right click a function and click "Create Unit Tests" Visual Studio 2015 decides to create a new Unit Test Project in the root directory of my solution. This means that if I want to create unit tests for all my code, I will end up having dozens of Unit Test Projects in the root of my solution - which makes things messy.
I created a Folder in my Solution called "Tests" and I want all new Test Projects to automatically end up inside this folder. How do I do this? Is it possible to set the location of where Unit Test Projects are created?
This problem is only when I right-click on exact test, and call Run Tests.
When I build projects, including project with tests, VS build only dependencies.
Is this normal?
I have set up a TFS 2010 Team Build Configuration to run continuous builds.
I currently have 2 Test Projects that run inside Visual Studio 2010 IDE with no problems.
When I queue the solution (with the test projects) to build, the build log reports:
"No Test Results".
My Build Process parameters Automated Test Rule matches my test assembly names:
Run tests in assemblies matching **\*_Test.dll.
After inspecting the Build folder C:/Builds/2/[ProjectName]/[BuildName]/Binaries, I noticed that there were no .dll/.pdb files for my test projects built; even though all other project required dlls are in here.
The Test Project folders do exist in C:/Builds/2/[ProjectName/[BuildName]/Sources.
My Build Process parameters referenced under "Items to Build" => "Configurations to Build" :
Any CPU|Relase
Under Configuration Manager for my soltuion, for Any CPU and Release, I Do have my Test Projects checked off under the Build column.
From all of the documentation I have read, my tests should be running, but from the above inspection it appears that they are not even building.
Any insight or ideas into getting these unit test projects to compile and run on my TFS 2010 Build Server would be greatly appreciated.
Thanks!
When setting up the build, you can point to the vsmdi file instead of putting in the wildcard. Does that yield the same result?