![]() the Test Impact collector, that enables the Test Impact feature. What is interested to see is enabling e.g. You can see the channel 9 video that shows more about coded UI testing if you want some more information on that new feature. While this is less interesting for a Unit test that has no UI interactions, this is very interesting when you create a new type of test called Code UI test that can run an previously recorded UI test and replay it on a test machine. the video recorder, you will get an video capture of your computer while the test was running. When you take a further look into the set of collectors you might also see a set of new collectors that you have not seen before. Now when you run another unit test you will see code coverage is now enabled. Here you need to pick the assembly that is under test and click “Ok” Then you will see the more familiar dialog again as shown below: ![]() In the 2010 dialog you can select the assemblies by first clicking on the “Code Coverage” row in the collectors list and then clicking the “Advanced…” button. In the 2008 ide you would direct see the assemblies that are part of the coverage gathering during the run. In this list you need to select the “Code Coverage” item and mark the enabled check box. Here you need to select the “Execution Criteria” in the left list and then you can see at the bottom of the page the set of collectors that are enabled for a test run. Open the Local.testsettings file and there you will see a set of items you can configure on the left hand of the dialog. In Visual Studio 2010 you need to take the following steps: When you want to Enable code coverage in an Unit test run in Visual Studio 2010 you may find that the steps you need to take have changed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |