Posts Currently viewing the tag: "Microsoft Test Manager (MTM)"

If you’re using Team Foundation Server’s Test Hub for your QA testing effort, you’ve probably seen this annoyance.  All of your test cases say “Windows 8” in the Configuration column.  Windows 8?!? What is this? 2014?!  You’ll hit your next level of frustration about 20 seconds later when you find out…(Read More)


Ok.  Microsoft Test Manager (MTM) isn’t going away but you might have noticed that it’s kind of been put out to pasture.  There were some good features – some core features – in MTM that were kind of helpful.  So what do you we do now?  If you’re on Team Foundation Server 2015 (TFS2015…(Read More)


I spoke at Microsoft TechEd 2014 in Houston, TX last week.  One of the talks I did was on using Team Foundation Server 2013 (TFS2013) and Microsoft Test Manager 2013 (MTM 2013) to test your software.  Specifically, how do you perform your tests and track your testing efforts so that you know that your application…(Read More)


I spoke at VSLive Orlando 2013 last month and did a talk called “Software Testing with Visual Studio 2013 and Team Foundation Server 2013”.  Software Testing with Visual Studio 2013 and Team Foundation Server 2013 Visual Studio 2013 and Team Foundation Server 2013 both have a major focus on testing and quality. There are…(Read More)


I’ve been part of an on-going discussion with some other Microsoft MVPs and Visual Studio team members about some headaches with Microsoft Test Manager 2012 (MTM 2012) and Microsoft Test Manager 2013 (MTM 2013).  As much as I like MTM, it can be a little frustrating to use.  On the other hand, Microsoft…(Read More)


I was visiting a new customer yesterday who is thinking of adopting Team Foundation Server 2010.  Amongst other things, they asked me for an overview of the SQL Server Reporting Services Reports –- specifically, which reports are good for Project Managers.  My first thought was the Stories Overview report. The Stories Overview report (see Figure…(Read More)


Summary: Silverlight Coded UI tests don’t work properly against UserControls unless you specify either AutomationProperties.Name or AutomationProperties.Id on the UserControl. (Thanks to Howie Hilliker @ Microsoft for his help figuring out this problem!) With the release of Visual Studio 2010 Feature Pack 2, we now have the ability to create Coded UI Tests…(Read More)