扩展Visual Studio Test Project：自定义TestClassAttribute - part 2

忘是亡心i 2021-12-20 23:49 231阅读 0赞

\[转\] [http://blogs.msdn.com/b/vstsqualitytools/archive/2009/09/04/extending-the-visual-studio-unit-test-type-part-2.aspx][http_blogs.msdn.com_b_vstsqualitytools_archive_2009_09_04_extending-the-visual-studio-unit-test-type-part-2.aspx]

代码下载地址：[http://archive.msdn.microsoft.com/UnitTestExtendSample/Release/ProjectReleases.aspx?ReleaseId=4030][http_archive.msdn.microsoft.com_UnitTestExtendSample_Release_ProjectReleases.aspx_ReleaseId_4030]

In [part 1][], we introduced Unit Test Type Extensibility, highlighting the main parts of the interface.  In this round, we will discuss three additional pieces:

1.  Adding a user interface
2.  Parameterizing the test method
3.  Aggregating test results
4.  UI extension

Due to the amount of code in this sample, I will paste some of it at the end of the blog.  The rest I will try to upload as a file to the blog.

#### The Finished Product ####

Lets begin again at the end.  “What do these three additional pieces give me?”

A snapshot seems appropriate here

[![image][]][image 1]

Yes, I know, unit test should already have this built into the standard implementation, but since we have not done this, one is able to build a very quick implementation of it for your own testing.

Lets go through this code.

1.  The **RowTestClass** attribute tells the framework to load my test type extension to run these tests       [![image][image 2]][image_image 2]
2.  We have a new custom attribute, called **Row**, that will allow me to pass in the data that I want to send to my parameterized test method       [![image][image 3]][image_image 3]
3.  Now, with our test method being parameterized, we can use those variables directly in our test method instead of having to pull them off the **DataRow** in the **TestContext** [![image][image 4]][image_image 4]

Lets blaze on ahead with the different files.  I will quickly show the References, TestClassAttribute, TestExtensionExecution, and parts of the Invoker.  We will dive deeper into the invoker, aggregation and UI code.

#### Row Test Test Type Extension : References ####

First we need the references.  The Microsoft.VisualStudio.QualityTools.UnitTestFramework assembly can be found in the Global Assembly Cache, and the other three Microsoft assemblies can be found in PrivateAssemblies.  For more information, see [Extending the Visual Studio Unit Test Type, part 1: Run As Extension : References][part 1] section

[![image][image 5]][image_image 5]

#### Row Test Test Type Extension : RowTestClassAttribute.cs file (quick view) ####

File number 1, RowTestClassAttribute.cs, is similar to the RunAsTestClassAttribute with the following differences:

[![image][image 6]][image_image 6]

1.  The **Uri** is unique to this attribute.
2.  In our **GetClientSide** implementation, we return a **RowTestExtensionClientSide** object. (see **Row Test Test Type Extension : RowTestExtensionClientSide.cs file**)

For more information, see [Extending the Visual Studio Unit Test Type, part 1][part 1] for more information regarding the **TestClassExtensionAttribute**.

#### Row Test Test Type Extension : RowTestExtension.cs file (quick view) ####

File number 2, **RowTestExtension.cs**, is similar to the **RunAsTestExtensionExecution.cs** file and there only difference is the object type returned, which is a **RowTestInvoker** class (see **Row Test Test Type Extension : RowTestInvoker.cs file (quick view)**)

[![image][image 7]][image_image 7]

#### Row Test Test Type Extension : RowTestInvoker.cs file (quick view) ####

File number 3, **RowTestInvoker.cs**, is similar to the **RunAsTestMethodInvoker.cs**, with the difference being in the **Invoke** method.

[![image][image 8]][image_image 8]

The **Invoke** method is where it gets interesting.

1.  First we initialize our **RowTestResults** class.  This class is used to aggregate our results when we execute them.       [![image][image 9]][image_image 9] 
2.  We then gather all the **RowAttributes** off the test method using reflection.[![image][image 10]][image_image 10]
3.  We then check the count of the **RowAttributes** we have.  If we don’t have any, we will invoke the base method passing a null as a parameter.       [![image][image 11]][image_image 11]
4.  If we do find a list of **RowAttributes**, we will iterate through them and call the Invoke method, passing the row information.  We also aggregate them into our the RowTestResults instance that we created in step \#1.      [![image][image 12]][image_image 12]
5.  Finally we return the single aggregated results     [![image][image 13]][image_image 13]

#### Row Test Test Type Extension : RowTestExtensionClientSide.cs file (quick view) ####

This file allows us to return the UserControl which will be displayed in the UI when the results details is requested.  It also has the icon we would like to use for our Test Type Extension.[![image][image 14]][image_image 14]

The **Icon** property returns an embedded Icon that I placed in the Resources for the project.

The **ResultExtensionViewer** returns the user control that we have created to display our results.

#### Row Test Test Type Extension : RowTestExtensionViewer.cs file (quick view) ####

This is a user control, so it also has a .Designer.cs and a .resx file with it.  However, the most important is the implementation of the User control.  It must implement **ITestTypeExtensionResultViewer**

[![image][image 15]][image_image 15]

Of note, the **Initialize** function is what makes this work.

1.  The initialize takes a **TestResult** argument.  This is will contain quite a bit of information regarding outcome, error, stack trace and other items you may need for that result.  But keep in mind, this is the overall result.  You can call it the result container.      [![image][image 16]][image_image 16]
2.  For our purpose we need to get a little piece of information off it regarding the ITestResultExtension.  So we cast it, check that it isn’t null and dump the results to it (since we returned a string earlier (see Row Test Test Type Extension : RowTestInvoker.cs file – Step \#5).     [![image][image 17]][image_image 17] This line also assumes that we have placed a label on our UserControl.

And that is it.  A little more work but now we are ready to deploy

#### Row Test Test Type Extension : Registering your test type extension ####

To make it all work you now need to place your test type extension assembly in the correct location and register your test type in the registry.

**Location**:  The location of your test type, and your PDB if you want, needs to be in the PrivateAssemblies location; the same one that contains the assemblies that we referenced in the beginning

[![clip\_image001][clip_image001]][clip_image001_clip_image001]

**Registry**: The test type needs to be in the following key:

\[HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\10.0\\EnterpriseTools\\QualityTools\\TestTypes\\\{13cdc9d9-ddb5-4fa4-a97d-d965ccfc6d4b\}\\TestTypeExtensions\\RowTestClassAttribute\]

The registry entry is a string called “AttributeProvider” and will contain your attribute and the name of your assembly.    "AttributeProvider"="DemoExtension.RowTest.RowTestClassAttribute, DemoExtension"

![image][image 18]

There is a second location that is usually populated when you start Visual Studio.  It is located under the following key: (NOTE the bolded text for the differences in the two keys)

\[**HKEY\_CURRENT\_USER**\\SOFTWARE\\Microsoft\\VisualStudio\\**10.0\_Config     ** \\EnterpriseTools\\QualityTools\\TestTypes\\\{13cdc9d9-ddb5-4fa4-a97d-d965ccfc6d4b\}\\TestTypeExtensions\\RowTestClassAttribute\]     "AttributeProvider"="DemoExtension.RowTest.RowTestClassAttribute, DemoExtension"

I place the second key in manually because sometimes it doesn’t do it for me straight away and I get impatient and cannot wait for the key to be updated.  The full registry file can be found at the end of the blog as **RowTestExtension.reg**

**FINAL REGISTRY NOTE:** If you are on an x64 machine, the registry key will be under the Wow6432Node as in HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft…

**FINAL LOCATION NOTE:** If you are on an x64 machine, the location key will be under the Program Files(x86) folder.

**WORKING WITH VS NOTE:** Because the test type is loaded within Visual Studio, developing the test type in addition to testing it poses problems when you need to update the test type extension assembly.  To make this work so you can develop in one instance of Visual Studio and test in a separate instance of Visual Studio, you can use the Visual Studio Development Experimental Model found [here][]

#### Summary ####

Good Luck!  Let us know if there are any questions or thoughts around this.  Hopefully extending the unit test type will be far easier than doing it from scratch like in Visual Studio 2008.  Doing a test type from scratch is still supported and sometimes needed, but if you can get along by using the test type extension, things will be much easier.

转载于:https://www.cnblogs.com/jenneyblog/p/CustomTestClassAttribute\_part2.html

[http_blogs.msdn.com_b_vstsqualitytools_archive_2009_09_04_extending-the-visual-studio-unit-test-type-part-2.aspx]: http://blogs.msdn.com/b/vstsqualitytools/archive/2009/09/04/extending-the-visual-studio-unit-test-type-part-2.aspx
[http_archive.msdn.microsoft.com_UnitTestExtendSample_Release_ProjectReleases.aspx_ReleaseId_4030]: http://archive.msdn.microsoft.com/UnitTestExtendSample/Release/ProjectReleases.aspx?ReleaseId=4030
[part 1]: http://blogs.msdn.com/vstsqualitytools/archive/2009/09/04/extending-the-visual-studio-unit-test-type-part-1.aspx
[image]: /images/20211220/79b811bbe0784aafa83f2eb5d71e8a03.png
[image 1]: http://blogs.msdn.com/blogfiles/vstsqualitytools/WindowsLiveWriter/ExtendingtheVisualStudioUnitTestTypepart_B1D9/image_2.png
[image 2]: http://blogs.msdn.com/blogfiles/vstsqualitytools/WindowsLiveWriter/ExtendingtheVisualStudioUnitTestTypepart_B1D9/image_thumb_1.png
[image_image 2]: /images/20211220/cbd9ae7cbdc048fea8746740b5ca1310.png
[image 3]: http://blogs.msdn.com/blogfiles/vstsqualitytools/WindowsLiveWriter/ExtendingtheVisualStudioUnitTestTypepart_B1D9/image_thumb_2.png
[image_image 3]: /images/20211220/b42f8c78137849ec963d1e96b1bc5eb1.png
[image 4]: http://blogs.msdn.com/blogfiles/vstsqualitytools/WindowsLiveWriter/ExtendingtheVisualStudioUnitTestTypepart_B1D9/image_thumb_3.png
[image_image 4]: /images/20211220/63d313dd6bac46ca8cc5c3db6f3cc55a.png
[image 5]: http://blogs.msdn.com/blogfiles/vstsqualitytools/WindowsLiveWriter/ExtendingtheVisualStudioUnitTestTypepart_B1D9/image_thumb_4.png
[image_image 5]: /images/20211220/5442ef509072477ab56ba51b1210e5dc.png
[image 6]: http://blogs.msdn.com/blogfiles/vstsqualitytools/WindowsLiveWriter/ExtendingtheVisualStudioUnitTestTypepart_B1D9/image_thumb_5.png
[image_image 6]: /images/20211220/5e8aa64c752844fcb77cc3ee7a29aa3a.png
[image 7]: http://blogs.msdn.com/blogfiles/vstsqualitytools/WindowsLiveWriter/ExtendingtheVisualStudioUnitTestTypepart_B1D9/image_thumb_6.png
[image_image 7]: /images/20211220/c7e116e5e48442d69fc1c70695baaac9.png
[image 8]: http://blogs.msdn.com/blogfiles/vstsqualitytools/WindowsLiveWriter/ExtendingtheVisualStudioUnitTestTypepart_B1D9/image_thumb_7.png
[image_image 8]: /images/20211220/262c060e497943be9d6b8400924c87ec.png
[image 9]: http://blogs.msdn.com/blogfiles/vstsqualitytools/WindowsLiveWriter/ExtendingtheVisualStudioUnitTestTypepart_B1D9/image_thumb_9.png
[image_image 9]: /images/20211220/e305027ce0f0493ebaed1b846e3f03bd.png
[image 10]: http://blogs.msdn.com/blogfiles/vstsqualitytools/WindowsLiveWriter/ExtendingtheVisualStudioUnitTestTypepart_B1D9/image_thumb_11.png
[image_image 10]: /images/20211220/c407132b20dc4467b024830911a22d77.png
[image 11]: http://blogs.msdn.com/blogfiles/vstsqualitytools/WindowsLiveWriter/ExtendingtheVisualStudioUnitTestTypepart_B1D9/image_thumb_12.png
[image_image 11]: /images/20211220/7a2c82797c614d3d893cd5b0b9ca664a.png
[image 12]: http://blogs.msdn.com/blogfiles/vstsqualitytools/WindowsLiveWriter/ExtendingtheVisualStudioUnitTestTypepart_B1D9/image_thumb_10.png
[image_image 12]: /images/20211220/908c6b9217734f7cb05c2b868c1e4851.png
[image 13]: http://blogs.msdn.com/blogfiles/vstsqualitytools/WindowsLiveWriter/ExtendingtheVisualStudioUnitTestTypepart_B1D9/image_thumb_13.png
[image_image 13]: /images/20211220/e2081f9e52d34c4897568c5dcb05f33f.png
[image 14]: http://blogs.msdn.com/blogfiles/vstsqualitytools/WindowsLiveWriter/ExtendingtheVisualStudioUnitTestTypepart_B1D9/image_thumb_14.png
[image_image 14]: /images/20211220/b417afa863f847d58400c89fcb4f4c73.png
[image 15]: http://blogs.msdn.com/blogfiles/vstsqualitytools/WindowsLiveWriter/ExtendingtheVisualStudioUnitTestTypepart_B1D9/image_thumb_16.png
[image_image 15]: /images/20211220/0ec885bed58d4c8c914bc757a2f7075e.png
[image 16]: http://blogs.msdn.com/blogfiles/vstsqualitytools/WindowsLiveWriter/ExtendingtheVisualStudioUnitTestTypepart_B1D9/image_thumb_17.png
[image_image 16]: /images/20211220/b3d418ea1fce4b8d8f112f2813a71c07.png
[image 17]: http://blogs.msdn.com/blogfiles/vstsqualitytools/WindowsLiveWriter/ExtendingtheVisualStudioUnitTestTypepart_B1D9/image_thumb_18.png
[image_image 17]: /images/20211220/fd02f5c93a9b4b7585a06a987817c32d.png
[clip_image001]: http://blogs.msdn.com/blogfiles/vstsqualitytools/WindowsLiveWriter/ExtendingtheVisualStudioUnitTestFramewor_F1DC/clip_image001_bd33a9d6-7abd-4fbc-bb15-fbd0795b8936.png
[clip_image001_clip_image001]: /images/20211220/04e8cc589a4a425b86497cc69fd94650.png
[image 18]: /images/20211220/b00d96a7474c4b1a81ec647dbf09f4f7.png
[here]: http://msdn.microsoft.com/en-us/library/bb166560%28VS.80%29.aspx