blocks|key|351985|text|在visual+studio中，将App.config文件标记为CopyAlways属性。(右击文件，选择属性进入属性面板)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|351986|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In visual studio, mark the App.config file to property to CopyAlways. (right click on file, choose properties to get to the property panel)

blocks|key|3131814|text|我以前从未使用过NoIsolation，但如果我没理解错的话，它确实可以运行MSTest类中的所有测试代码。在这种情况下，它确实也应该读取MSTest的应用程序配置。如果您坚持使用MSTest.exe.config，我认为您必须将您的App.config合并到noisolation中。当然，这是一种黑客行为。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3131815|完全避免这种非隔离可能会更好。如果是由于错误导致的，请尽可能修复错误。如果无法重新组织(主要重构)您的应用程序，请解决此错误。我不确定是否有一个优雅的替代方案。|3131816|我发现“我认为我们需要找到这个问题的根本原因，以避免noisolation开关。你可能需要修改你的应用程序。是否有可能创建一个简单的解决方案来再现相同的问题？”在this+URL。|offset|length|3131817|entityMap|0|LINK|mutability|MUTABLE|url|http://social.msdn.microsoft.com/Forums/en-US/vststest/thread/a15f8a4b-b869-4a35-ac72-57f783bdd7b7/^0|0|0|29|8|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

I've never before used NoIsolation, but if I am understanding it correctly, it literally runs all of your test code in the MSTest class. That being so, it does and should read the App config for MSTest. If you insist on using noisolation, I'm thinking you would have to merge your App.config into MSTest.exe.config. Of course, that is a hack.

It would probably be better to avoid the noisolation altogether. If it is due to an error, fix the error if possible. Work around the error if reorganizing (major refactoring) your app is not possible. I'm not sure there is an elegant alternative.

I found "I think we need to find the root cause of this issue in order to avoid the noisolation switch. You might need to modify your applicaton. Is it possible to create a simple solution that repro the same issue?" at <a href="http://social.msdn.microsoft.com/Forums/en-US/vststest/thread/a15f8a4b-b869-4a35-ac72-57f783bdd7b7/" rel="nofollow noreferrer">this URL</a>.

blocks|key|354660|text|有一种技术可以组合配置文件的内容，它是详细的here。您可以在MSTest.exe.Config中添加一个固定的文件包含行，然后将应用程序的app.config复制到该固定文件位置。它很难看，但比黑客攻击MSTest.exe.Config更便于处理任何不同的情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|354661|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/89245/how-do-you-manage-net-appconfig-files-for-large-applications^0|M|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

There's a technique where you can combine the contents of config files it's detailed <a href="https://stackoverflow.com/questions/89245/how-do-you-manage-net-appconfig-files-for-large-applications">here</a>. You could add a fixed file inlcude line to MSTest.exe.Config, and then copy your app's app.config to that fixed file location. It's ugly, but more portable than hacking MSTest.exe.Config for every different eventuality.

blocks|key|3131887|text|在http://docs.ncover.com/ref/2-0/whats-new-in-ncover-2-0/release-notes-for-ncover-2-1-0/的NCover修复下：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3131888|在MSTest上运行覆盖不再需要"/noisolation“标志。NCover正确地收集覆盖率|3131889|如果确实修复了此问题，请将NCover升级到2.1.0。也许这会奏效。|3131890|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.ncover.com/ref/2-0/whats-new-in-ncover-2-0/release-notes-for-ncover-2-1-0/^0|1|2E|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

At <a href="http://docs.ncover.com/ref/2-0/whats-new-in-ncover-2-0/release-notes-for-ncover-2-1-0/" rel="nofollow noreferrer">http://docs.ncover.com/ref/2-0/whats-new-in-ncover-2-0/release-notes-for-ncover-2-1-0/</a> under NCover Fixes:

Running coverage on MSTest no longer requires the "/noisolation" flag. NCover correctly gathers coverage 

If this is indeed fixed, then upgrade NCover to 2.1.0. Perhaps that will work.

blocks|key|3131913|text|好吧，我冒着我的帖子会变成单元测试火焰墙的风险，但我认为问题出在你的测试，甚至可能是你的代码。你应该重构。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3131914|单元测试应该是原子的。一个测试应该没有外部依赖项，而配置文件是这样的依赖项。任何测试都不应该依赖于配置文件。|offset|length|style|BOLD|3131915|如果要测试的方法使用配置文件中的信息，请重构代码，以便在方法外部读取配置的信息，并在调用该方法之前将其传递给该方法或设置为属性。这样，您的测试既可以将值传递给方法，也可以在测试设置期间设置该属性。|3131916|如果您需要使用app.config作为数据库连接字符串，您可以自行完成。众所周知，DAL很难进行单元测试。如果它用于web服务连接字符串，请不要使用它--模拟接口。|3131917|entityMap^0|0|U|1|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

Ok, I'm running the risk that my post will devolve into a unit testing flamewar, but I think the problem is your tests and possibly even your code. You should refactor. 

Unit tests should be atomic. A single test should have no external dependencies and a config file is such a dependency. No test should rely on the config file. 

If you are testing a method that uses information from a config file, refactor your code so that the configured information is read outside of the method and either passed to the method or set as a property before the method is called. That way your test can either pass the value to the method, or set the property during test setup. 

If you need your app.config for a database connection string, you're on your own. DALs are notoriously difficult to unit test. If it's for a web service connection string, don't use it -- mock the interface.

blocks|key|3344731|text|为了消除混淆:不使用/noisolation+=如果它找到SameNameAsYourDll.dll.config文件，它将自动与测试dll一起部署，并将用于运行该程序集中测试的应用程序域的应用程序配置|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3344732|使用/noisolation+=我们在测试之间所做的所有隔离，您、主机进程和其他一切都不在窗口之外。我们可能仍然会进行一些隔离，但您不会获得应用程序域对于您的测试dll是唯一的附加好处。因此，您的dll的配置将不会有帮助。|3344733|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

To clear up the confusion:
not using /noisolation = if it finds a SameNameAsYourDll.dll.config file, it'll be deployed with the test dll automatically, and will be used for the app config for the app domain that runs the tests in that assembly

using /noisolation = All the isolation we do between tests, you, the host process, and everything else is out the window. We may still do some isolation, but you don't get the added benefit of the app domain being unique to your test dll. Thus, you dll's config won't help.

blocks|key|349744|text|来自克雷格·斯顿茨在link+text上的评论|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|349745|如何使用MSTest做到这一点。|349746|在解决方案资源管理器中，右键单击解决方案(不是“Project).|349747|Click+Add”，在“Categories”中选择“Configuration|unordered-list-item|349748|
|349749|Now+|349750|349751|349752|349753|”，选择“Test+Run”并选择“Test+Run+Configuration”并将其添加到解决方案资源管理器中的项目|349754|349755|中，然后双击“Test+Run+Configuration+you+just+created|349756|349757|Click+|349758|
+Deployment+item+|349759|”将配置文件添加为已部署文件(或部署包含该文件的整个文件夹，如果为appropriate)|349760|349761|这花了我一点时间才弄明白，但我处于类似的情况下，它确实对我有效。|349762|entityMap|0|LINK|mutability|MUTABLE|url|http://devlicio.us/blogs/derik_whittaker/archive/2008/07/23/mstest-why-i-hate-you-you-cause-me-too-much-friction.aspx^0|A|9|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1E|8|@]|9|@$A|1F|B|1G|1|1H]]|C|$]]|$1|D|3|E|5|6|7|1I|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|1J|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|1K|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|1L|8|@]|9|@]|C|$]]|$1|M|3|N|5|J|7|1M|8|@]|9|@]|C|$]]|$1|O|3|L|5|6|7|1N|8|@]|9|@]|C|$]]|$1|P|3|-4|5|J|7|1O|8|@]|9|@]|C|$]]|$1|Q|3|L|5|6|7|1P|8|@]|9|@]|C|$]]|$1|R|3|S|5|J|7|1Q|8|@]|9|@]|C|$]]|$1|T|3|L|5|6|7|1R|8|@]|9|@]|C|$]]|$1|U|3|V|5|J|7|1S|8|@]|9|@]|C|$]]|$1|W|3|L|5|6|7|1T|8|@]|9|@]|C|$]]|$1|X|3|Y|5|J|7|1U|8|@]|9|@]|C|$]]|$1|Z|3|10|5|6|7|1V|8|@]|9|@]|C|$]]|$1|11|3|12|5|J|7|1W|8|@]|9|@]|C|$]]|$1|13|3|-4|5|6|7|1X|8|@]|9|@]|C|$]]|$1|14|3|15|5|6|7|1Y|8|@]|9|@]|C|$]]|$1|16|3|-4|5|6|7|1Z|8|@]|9|@]|C|$]]]|17|$18|$5|19|1A|1B|C|$1C|1D]]]]

From Craig Stuntz in a comment at <a href="http://devlicio.us/blogs/derik_whittaker/archive/2008/07/23/mstest-why-i-hate-you-you-cause-me-too-much-friction.aspx" rel="noreferrer">link text</a>

How to do this with MSTest.

<ol>
<li>In Solution Explorer, right-click the Solution (not the Project).</li>
<li>Click Add, New Item</li>
<li>In Categories, select Test Run Configuration</li>
<li>Now choose the Test Run Configuration item and add it to your project</li>
<li>In Solution Explorer, double-click the Test Run Configuration you just created</li>
<li>Click the Deployment item</li>
<li>Add your config file as a deployed file (or deploy the entire folder which contains it, if appropriate)</li>
</ol>

This took me a little while to figure out, but I'm in a similar situation and it does work for me.

blocks|key|351014|text|我在使用MSTestRunner+Plugin的Jenkins版本中也遇到了同样的问题。选中从配置页中忽略NoIsolation解决了此问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|351015|entityMap|0|LINK|mutability|MUTABLE|url|https://wiki.jenkins-ci.org/display/JENKINS/MSTestRunner%2BPlugin^0|4|J|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I had the same problem in Jenkins builds with <a href="https://wiki.jenkins-ci.org/display/JENKINS/MSTestRunner+Plugin" rel="nofollow">MSTestRunner Plugin</a>. Checking Omit NoIsolation from configuration page solved the problem.

blocks|key|3344849|text|尝试将其名称从app.config更改为projectname.extension.**config**|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3344850|例如，如果您有一个名为proj1的单元测试项目并使用其dll，则将app.config重命名为proj1.dll.config|3344851|这对我很有效。|3344852|entityMap^0|7|A|K|W|0|B|5|R|3|X|A|1B|G|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|Z|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|K|$]]

Try changing its name from <code>app.config</code> to <code>projectname.extension.**config**</code>

For example, if you have a unit test project named <code>proj1</code> and you use its <code>dll</code>, rename <code>app.config</code> to <code>proj1.dll.config</code>

This worked for me.

I'm currently trying to run MSTest.exe from NCover, but I believe the question could apply generally to running MSTest.exe from the command line.

If I have the "/noisolation" argument, then MSTest.exe appears to find and use the app.config as expected. Without it, NCover doesn't capture any coverage information. From my research so far, it seems NCover needs /noisolation. So the question is how to get my *.config files to work when that argument is passed.

My NCover settings are:

Application to Profile 
C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\MSTest.exe

Working Folder 
C:\Documents and Settings\MyProfile\My Documents\Visual Studio 2008\Projects\XYZ\XYZ.CoreTest\bin\Debug

Application arguments 
/noisolation /testcontainer:"C:\Documents and Settings\MyProfile\My Documents\Visual Studio 2008\Projects\XYZ\XYZ.CoreTest\bin\Debug\XYZ.CoreTest.dll"

 
Update: I added a trace showing that my config is (not surprisingly) trying to read from "C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\MSTest.exe.Config".

Update 2: If at all possible, I don't want to edit MSTest.exe.Config. That just isn't terribly portable.

MSTest.exe not finding app.config

Visual Studio

单元测试

数据库

我目前正在尝试从NCover运行MSTest.exe，但我相信这个问题通常适用于从命令行运行MSTest.exe。如果我有"/noisolation“参数，那么MSTest.exe似乎可以按预期查找和使用app.config。如果没有它，NCover不会捕获任何覆盖信息。到目前为止，根据我的研究，NCover似乎需要/...

问MSTest.exe找不到app.config
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MSTest.exe找不到app.configEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MSTest.exe找不到app.config
EN