The Configuration column says “Windows 8”, right? Why the heck does it say Windows 8? I’m not testing on Windows 8…so how do I change that? Well, through the web interface, you can’t. Go into the test hub and create a couple of Test Cases and then look in the Configuration column. The biggest thing that’s missing from the web interface is Test Configurations. Microsoft is definitely going in a good direction with that plugin though. Last time that I checked, it was still in beta and as such it still had some sharp edges. It’s pretty good and it gives you the ability to do screenshots and video recording, too. If you want to do more free-form exploratory testing, there’s a new Exploratory Testing client for Chrome. It only works with certain types of Windows application technologies and for web apps it only works with Internet Explorer. In real life, it’s still pretty limiting and brittle. That Action Recordings feature makes for some jaw-droppingly awesome demos. The idea with Action Recordings is that a non-technical QA person would be able to create automated tests that help speed up the QA testing process and eliminate QA testing tedium. Using the MTM Test Runner also lets you continue to do lightweight test automations using MTM Action Recordings. Microsoft split that test execution functionality into its own EXE so you can still do all that great stuff. This makes sense because the really handy stuff from the MTM Test Runner was the ability to create really descriptive bugs that contained screenshots and video recordings. Longer answer: you’re done with using MTM to plan and track your tests but you still have the option to run tests using the MTM rich test client. At this point you’re thinking, “didn’t you just say that we’re pretty much done with MTM?” Short answer: yes. You’ve now got two options for running tests: 1) run test cases using the web interface and 2) run test cases using the MTM client. TFS Build vNext and TFS Release Management work in concert to get stuff deployed on to servers and the integration with the QA tools are now entirely optional. (NOTE: those XAML-based builds are still there but there’s a new build system that’s a lot easier to use.) The deployment features of Lab Management have been moved in to TFS Release Management. The build system that was at the core of Lab Management has changed. The second biggest change is that Lab Management is done. Want to see the status of a test case? It’s right there in the user interface. Want to run a test? Click the Run button. Want to plan a test? Create one or just start editing an existing one. There’s no longer an artificial separation between planning your tests, running your tests, and tracking the results – everything is in one, unified interface. The biggest change is that pretty much everything’s moved to the web and you no longer have to fight your way through MTM’s nonsensical user interface design. What’s changed?īefore we start discussing what’s changed and what’s gone/going away, I just want to say that life is better now and the tooling is so MUCH better now. Put those two huge changes together and it’s a no-brainer that Microsoft had to take their QA/Manual testing tools in a different direction. MTM was written before Microsoft Azure or Amazon took off in the cloud space. How we manage our virtual test labs is vastly different now. Test case management is pretty much still the same but what we’re testing is a lot more varied and cross-platform. The world has changed a lot since MTM came out – TFS is no longer laser-focused on Windows-only development and cloud computing is huge. Mission #1: test case planning, management, & execution. It’s been around for a long time and while it’s a great tool, it’s infamous for having a difficult and confusing user interface mostly because it had two missions that were only loosely related. Microsoft Test Manager (MTM) is the “rich client” for QA and Manual Testing that hooks in to TFS. So what do you we do now? If you’re on Team Foundation Server 2015 (TFS2015) what’s missing? What’s your strategy for the future? How did we get here? There were some good features – some core features – in MTM that were kind of helpful. Microsoft Test Manager (MTM) isn’t going away but you might have noticed that it’s kind of been put out to pasture.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |