How to enable code coverage in my Team Build

Problem: I am not getting code coverage results in my build. Solution: Ensure you have a test settings file selected in your build definition. Explanation: On the process tab of your build definition expand the Automated Testing section under Basic and make sure the TestSettings File is pointing to the test settings file that has code coverage configured. You can watch a video below that demonstrates how to do this.

CUIT Demo of Feature Pack 2 Coded UI Test Editor

Problem: I have a Coded UI Test that is failing on Playback. Solution: Use the Coded UI Test Editor in Feature Pack 2 to adjust the UI Map and add actions to your test. Explanation: I felt a write up would be too hard to follow so I recorded a video instead which you can watch below. In this video we are going to cover a few features of the Coded UI Test Editor available in Feature Pack 2 for Visual Studio 2010. The Coded UI Test Editor greatly improves an automation engineers experience working with Coded UI Test. The features we are going to demonstrate today are splitting actions into separate methods, renaming methods and locating UI controls in a running application. Many coded UI demos show you the happy path scenario where everything works perfectly.  While helping clients implement Coded UI Test in the real world you quickly realize that the happy path can be hard to stay on.  The goal of this web cast is to show a recording that does not work as recorded and techniques we can use to adjust the recording to yield the desired results.

I don't want Entity Framework code counted in code coverage.

Problem: The code generated by the Entity Framework is distorting my code coverage numbers. Solution: Add a Code Generation Item and add the [DebuggerNonUserCode] attribute to the generated classes. Explanation: As I described in a previous post here the [DebuggerNonUserCode] hides the code from code coverage results.  I am a huge fan of code coverage however; I do not see the point in testing generated code especially when most of it is just value objects. Entity Framework uses T4 Text Templates to generate the typed ObjectContext and EntityObject derived entity classes used in your code.  If the code generated does not fit your needs you can add a Code Generation Item to your project and the Entity Framework will use your custom T4 Text Template to generate the classes. Adding a new Code Generation Item is very easy.  Simply open your .edmx file and right click on the design surface and select Add Code Generation Item… from the context menu.  When the Add New Item dialog is presented select the Code section under your language of choice.  You will be presented two generator templates to choose from.  The ADO.NET EntityObject Generator template generates the same code as the default code generated by the Entity Framework Designer.  In solution explorer you will see a new file with a .tt extension.  This file will create a .cs (or .vb) file which appears under the .tt file in Solution Explorer. All we have to do now is modify the template by adding a using statement for System.Diagnostics and add the [DebuggerNonUserCode] attribute on all the partial classes in the template (there are 3). With the template in your solution all the Entity Framework code will be generated with the [DebuggerNonUserCode] attribute and removed from the code coverage calculations.   You can download a copy of the T4 Template below. Model1.tt (45.02 kb)

How to create a custom Value Provider for MVC

Problem: I need to test an MVC Controller Action that needs the Identity of the current user without mocking the HTTPContext. Solution: Create a custom Value Provider that allows access to the current user via an Action Parameter. Explanation: One of the goals of the MVC pattern is making the application easier to test.  Simply using the pattern does not grantee your application will be easy to test.  The application must be designed with testing in mind.  This does not require that you use Test Driven Development (TDD) but I do believe you must be what I like to call "Test Aware".  You must constantly be thinking during your design how are we going to test this? Does this design lend itself to easy testing?  Testing can no longer be an afterthought. While recently working on a MVC project I ran into an issue that was going to be very difficult to test because it relied on the read only User property of the Controller base class.  My goal was to find a way to allow my action to be tested without having to Mock the HTTPContext.  The action I was testing required Authorization and used the User.Identity property to query information from the data store.  Because the User property of the Controller base class is ready only I was unable to set it in my unit test which would require me to mock the HTTPContext to test that action. MVC Controllers have several mechanisms for receiving data.  You can access the data from context objects, invoke the framework's model binding feature or have the data passed as parameters using a value provider.  I prefer my action methods to have data passed as parameters.  When your action depends only on the parameters, without accessing context data directly they become much easier to understand and test.  Actions that only depend on their parameter are called "Pure". When your action method accepts parameters the framework employs the help of a collection of Value Providers and Model Binders to locate suitable values.  Like many components in the MVC framework Value Providers and Model Binders are pluggable.  This flexibility in the MVC framework allows developers to replace or extend the framework.  My solution was to simply create a custom Value Provider that would allow me to access the current user as an input parameter to my action method. Below is an example of the way the action would be written if you access the User property of the Controller base class.[Authorize]public ActionResult Index(){   Models.Userdetails clerk = context.Userdetails.Where(u => u.Username == User.Identity.Name).Single();   return View(context.Citations.Where(c => c.ID == clerk.ID &&                                             string.IsNullOrEmpty(c.UploadedBy)));}However, to test this method would be very difficult.  Instead I decided to write my action method so that it accepts a GenericPrincipal object as a parameter.[Authorize]public ActionResult Index(GenericPrincipal currentUser){   Models.Userdetails clerk = context.Userdetails.Where(u => u.Username == currentUser.Identity.Name).Single();   return View(context.Citations.Where(c => c.ID == clerk.ID &&                                             string.IsNullOrEmpty(c.UploadedBy)));}By writing the method this way I was able to create my test method without having to mock anything.[TestMethod]public void Index(){   // Arrange   HomeController controller = new HomeController();   // Act   GenericIdentity id = new GenericIdentity("userName");   GenericPrincipal user = new GenericPrincipal(id, null);   ViewResult result = controller.Index(user) as ViewResult;   // Assert   ViewDataDictionary viewData = result.ViewData;   Assert.IsTrue(viewData.Model is IEnumerable<Models.Citations>);}To achieve this design I had to extend the Value Providers with a custom class.Writing a custom Value Provider is very simple.  You simply create a class that implements the IValueProvider interface.  The IValueProvider interface only has two methods:•    ContainsPrefix - This is your value providers way of letting the MVC framework know you can handle this item.•    GetValue - If you return true from ContainsPrefix this method will be called to provide the value.To allow the MVC framework to access your value provider you must provide a ValueProviderFactory class as well.  This class derives from ValueProviderFactory and simply returns an instance of your Value Provider. The code below shows both the Value Provider Factory and the Value Provider.public class CurrentUserValueProviderFactory : ValueProviderFactory{   public override IValueProvider GetValueProvider(ControllerContext controllerContext)   {      return new CurrentUserValueProvider();   }   private class CurrentUserValueProvider : IValueProvider   {      public bool ContainsPrefix(string prefix)      {         return "user".Equals(prefix, StringComparison.OrdinalIgnoreCase);      }      public ValueProviderResult GetValue(string key)      {         return ContainsPrefix(key)            ? new ValueProviderResult(HttpContext.Current.User, null, CultureInfo.CurrentCulture)            : null;      }   }}The final step is to register your Value Provider Factory with the MVC framework.  Add the highlighted code to the Application_Start method inside Global.asax.cs protected void Application_Start(){   AreaRegistration.RegisterAllAreas();   RegisterRoutes(RouteTable.Routes);   ValueProviderFactories.Factories.Add(new Classes.CurrentUserValueProviderFactory());}This adds your custom Value Provider to the MVC framework and allows you to gain access to the current user in any action method by simply having a GenericPrincipal user parameter.

Why is my MS Project run so slow when connected to TFS.

Problem: With MS Project connected to TFS Project takes forever to refresh. Solution: One possible solution is to change the calculation mode from automatic to manual.  To change the calculation mode select Tools / Options / Calculation / Calculation Mode and change from automatic to manual.

Having trouble testing my WPF app with Coded UI Test

Problem: I cannot find my WPF TextBlock using the Coded UI test because the value is data bound and changes. Solution: Set the Name attribute on the controls of your View which sets the AutomationId. Explanation: Many WPF developers only place the Name attribute on items they intend to access from a code behind.  With most WPF developers using MVVM and trying to keep their Views as light as possible there would be no need to use the Name attribute.  However, if you intend to use Microsoft's new Coded UI test to test your view the Name attribute is important. The Coded UI test uses the Accessibility Framework to locate the controls on the screen.  The more distinct attributes the item has the more likely the test will be able to locate that control during playback. The Name attribute on WPF controls sets the AutomationId and allows it to be used to locate the control.  This is important when the value of for example a TextBlock changes.  If the Name attribute is not set the actual content of the TextBlock which is going to be changing during execution will make it almost impossible to locate that control during playback

I can't generate MySQL DDL from my Entity Framework edmx file.

Normal 0 false false false EN-US X-NONE X-NONE /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin-top:0in; mso-para-margin-right:0in; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0in; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} Problem: I have installed the MySql .NET Connector but when I try to generate a database from my Entity Framework model it only generates DDL for SQL Server. Solution: You must change the DDL Generation Template for the Model.  Open your edmx file and right click on the design surface and select Model Browser from the context menu.  Now in the Model Browser right click on the model and select Properties.  In the Properties window change the DDL Generation Template from SSDLToSQL10.tt (VS) to SSDLToMySQL.tt (VS).

I need to show TFS history of a file on the command line so I can redirect to a text file.

Problem: When I run the tf history command from the command line it shows a dialog box. Solution: Add the /noprompt option to the TF History command. This will cause the output to be shown in the command window. You can then use DOS redirection to easily store the results in a text file. For example: tf history $/MyProject/Main/Source /recursive /noprompt /format:detailed /collection:http://MyTFS:8080/tfs/defaultcollection > history.txt This will result in a new file called history.txt to be created in the working folder. Explanation: The key to not showing the dialog box is the /noprompt.  If you leave off the /noprompt you will be shown a dialog box. The output redirection operator > is used to send the command output to somewhere other than the screen for example a text file. > somefile.txt (If the file already exists it will be overwritten.)>> somefile.txt (This will append a file. If the file does not already exist it will be created.)

I have code I don't want used to calculate code coverage or code metrics

Problem: I have code that I don't want to be calculated in my code coverage results and/or my code metrics. Solution: Apply the GeneratedCodeAttribute, DebuggerNonUserCode or DebuggerHidden attributes to the specific code. Explanation:   GeneratedCodeAttribute DebuggerNonUserCode DebuggerHidden Code Metrics Excludes code No Effect Code Analysis Excludes code No Effect Code Coverage No Effect Excludes code

How to add a SharePoint portal after you created the Team Project

Problem: I created a team project and did not select the option to create a share point site and now I want to add one. Solution: Create a dummy site and remove the link to sharepoint and wire it up to the original team project. Or two create a new site in SharePoint and wire it up. Explantion: There is a great write up here on how to do both options.