search

shekharpro / mb-unit

Automatically exported from code.google.com/p/mb-unit
0 stars 0 forks source link

MSTest is running tests inside the temp folder instead of the original location. #357

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Reported by DoniG on gallio-dev mailing list.

Original issue reported on code.google.com by jeff.br...@gmail.com on 13 Dec 2008 at 8:20

GoogleCodeExporter commented 8 years ago

Original comment by jeff.br...@gmail.com on 13 Dec 2008 at 8:20

GoogleCodeExporter commented 8 years ago 
Issue 359 has been merged into this issue.

Original comment by jeff.br...@gmail.com on 4 Mar 2009 at 6:02

GoogleCodeExporter commented 8 years ago 
This is actually by design of MSTest.  So the issue is really to enable a 
little more
control over whether and how we do MSTest test resource deployment.

Original comment by jeff.br...@gmail.com on 13 May 2009 at 11:44

GoogleCodeExporter commented 8 years ago 
Issue 280 has been merged into this issue.

Original comment by jeff.br...@gmail.com on 13 May 2009 at 11:44

GoogleCodeExporter commented 8 years ago

Original comment by jeff.br...@gmail.com on 29 Jun 2009 at 8:33

GoogleCodeExporter commented 8 years ago 
I am sorry to say that I cannot provide the requested behavior.  MSTest is not
NUnit/MbUnit/xUnit/etc..  MSTest's preferred mode of operation is to deploy test
assemblies and other deployment items over to another folder in a temporary 
location.
 MSTest is under control of this process and there is nothing that Gallio can do to
prevent it or change it without without breaking a lot of MSTest functionality 
or
making the behavior inconsistent with running tests inside Visual Studio.

(Translation: If you want different semantics then I recommend using a 
different test
framework.)

So what I have done for Gallio v3.1 is to fix several issues related to the use 
of
deployment items, data-driven tests, and debugging.  

To ensure that dependent resources get copied over into that temp folder, use
MSTest's [DeploymentItem] attribute.  This should all work fine now (but it was
broken before).

NB. If you use [DeploymentItem] be sure to specify paths relative to the 
directory
where the compiled test assembly is located.  Don't specify paths relative to 
the
solution.

Original comment by jeff.br...@gmail.com on 16 Aug 2009 at 4:53