About the *.vsmdi files; did you had in mind “Team of Developers” when you assigned these files to the solution?

I don’t want to be understood wrong, the unit tests in VS.NET 2005 are amazing, but there are some small things that just do not make sense.

< xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /> 

I am a developer, who is writing code, and some basic unit test for this code, all what I want to do, is right click the test cases and select debug or run.

 

But this is not possible in VS.NET 2005, don’t ask me, no idea why, maybe there is a reason behind that, this is just my first week with 2005.

 

But I am so use to that, NUNIT’s add-in for VS.NET 2003 does it!

 

Anyway, I found that I can select a specific test from the “Test View” tab, and run it, and that immediately resulted to a new file under the solution directly with the extension of “*.vsmdi”.

 

Do you think this is correct in a team environment, where there are multiple developers writing code and multiple people testing

 

Does every one of them should check out the solution just to adjust the UI of VS.NET I mean the (Test View) tab.

Can anyone tell us what is the idea of having this file shared for everyone and checked out by everyone when they are using their own tab of “Test View”



Answer this question

About the *.vsmdi files; did you had in mind “Team of Developers” when you assigned these files to the solution?

  • TKV

    Hi,

    Thanks for your feedback.

    The .vsmdi file is normally created and added to the solution at the time the Test Project is created. You can see this by loading up VS, select File | New Project and create a new, say, C#, Test project. You will see the test project created, alongside with the .vsmdi file and a .testrunconfig file.  Therefore, when adding the solution to source code control, the .vsmdi file will be added as well. Under normal circumstances, using test view to execute tests should not cause this file to be created.

    Can you please confirm that this file did not exist before you started using the Test View   If so, it is likely a bug. Maybe the file was created but it was subsequently removed, and we need to add it back before certain operations can complete. If that's the case, once the file is added to source control and everyone has a copy, it shouldn't be created over and over again.

    Thanks.
    Winnie

  • About the *.vsmdi files; did you had in mind “Team of Developers” when you assigned these files to the solution?