visual studio - Running unit tests from within VS2008 vs using mstest on the command line -

-

I had some inconsistencies in running VS 2008 vs. Unit Test against the running of the same unit test with MSTES on the command line recently. Have faced. / P>

My scenario is a bit advanced, so I've probably hit some corners. I have many data driven unit tests running against the same datasource. I like to experiment with PostShare, so I have a PostSharp aspect - TestDataSource is written - which I apply to the unit test type, not the unit test methods. When the type is created, this aspect gives the PostSHORA instructions to attach the "Code> DataSource attribute to each type of unit examination method.

Checking the assembly built in the reflector It is found that each test method is credited with the correct DataSource attribute, running the test with the mstest on the command line behaves as expected - each test specifies the data It is run against the source.

However, the VS2008 fails to run the exact same unit test to find the data source. It appears that the VS-2008 ignores the assembly created and the source Code, which is definitely not a data driven trial, because the datasource attribute is injected during creation.

There is no problem with the deployed items < Code> DatasO

Text "Itemprop =" text ">

If you put a breakpoint in your test and observe the list of loaded modules, then you should see which debugging is the correct path to the assembly. Is this expected (in bin \ debugged)? If you open this file using Debugger's moving reflector, do you see PostSharap stuff inside?

It is astonishing that a part of the post-city unit tests has been written for MSTE and they run from Visual Studio without the problem. ..