Microsoft NZ has started a monthly Developer Tools webinar. Featuring yours truly we talk about what’s new in Visual Studio, ALM and all things Dev Tools. You can check out the first edition here - http://blogs.msdn.com/b/joenewton/archive/2013/10/01/nz-developer-tools-webinars.aspx
The first episode focuses on a Tech-Ed wrap-up, MTM 101, and a demo of the awesome new BrowserLink feature.
Coming up in October is Visual Studio 2013, and in November we will be focussing on the Visual Studio launch. Feedback would be appreciated, and if you have any topics that you think would like to see included please get in touch!
I was interviewed by Microsoft as part of their Developer Stories section on the Microsoft.com site.
They selected developers using .NET technologies and wanted to get background information about their views and background history.
Not many developers have Rob Maher’s geographic diversity. Born in Great Britain, he’s worked everywhere from the Philippines and Singapore to Saudi Arabia and the United States. A self-described “serial conference organizer,” he also regularly oversees Scrum, Kanban and Microsoft-related events in his adopted country of New Zealand.
“Fortunately, my wife and four-year-old son like traveling too,” he says.
See the full interview here:-
I am proud to say that I woke up to an email this morning letting me know that I have been renewed as a Microsoft ALM MVP for a 3rd year. Being part of a great community is the biggest benefit of this award.
The award is for ‘exceptional technical community leaders who actively share their high quality, real world experience with others’ Which is a very long way to say that MVP’s are active in their communities trying to share their knowledge.
I think that the direction that Visual Studio / Team Foundation Server is following right now makes it one of the most exciting products. 3 weekly drops of new features to Team Foundation Service certainly keeps things interesting! Here’s to a great year.
A while ago I published a post on how to create a build definition for Team Foundation Server 2010 that only ran the tests that had been identified by Test Impact Analysis. This is useful if your tests take a very long time to run, or you have a huge amount of tests and want quick feedback for your intra day builds.
This will work on the Team Foundation Service build system also.
I have had a few requests to get this updated for 2012/2013 and so here it is.
Things to remember:-
The testing system is a little different now than in 2010. When you create your build from the custom xaml and choose the process parameters go to the Add/Edit Test Run section.
You need to make sure that you select the MSTest.exe Runner. Test Impact Analysis is only supported by MSTest so if you don’t change this it won’t work. Also make sure that you select a .testsettings file also.
Remember that periodically (perhaps every night) you need to run a build, and change the IsBaseLine run parameter from False to True. This is what collects a base line of Test Impact data to measure your changes against. This will run all of your tests. They must all pass to gather the impact data.
Here is example output from my build. Notice that it has run 2 tests and there is no impact data.
We now have our baseline.
Once you have that you can run the build with the defaults and if you have changed some code that impacts a test it should appear.
In my example I have changed some code that will impact one test, and re-run the build.
Notice that the build only ran one test this time. The Impacted Tests section shows me which test was impacted and if i click on the Test run i see this.
So the build correctly ran the single impacted test. One last improvement over 2010, if you click on the “1 code change(s)” link on the Build report in the Impacted Tests section you see this
A nice summary of what was changed (with a link to the changeset and code diff) and the method name was changed etc. Much better!
The xaml is here. Any questions let me know.