For the first time in my testing career I'm finally using the entire Microsoft suite of tools for testing. In my past testing experiences I've had access to a tool, or part of one, but never a single-focused, full tool set. I've only scratched the surface of possibilities. For instance, TFS and MTM provide a complete MS tool suite for Agile software development, kanban board task tracking, coding, test development, test management and test tracking. Add SQL Server to the testing toolbox to cover database testing needs. Our team is starting to explore testing within Visual Studio, both manually and via automation. I'll share some tips that save time and reduce waste, while providing a well-organized software development management structure.
Development management and task boards
Microsoft Team Foundation Server (TFS) provides all the tools necessary to manage a software development project in a single tool. Teams can create development space using xxx. XXX allows teams to post notes and communicate whether they're located in the same office or geographically dispersed. XXX has a social media feel and includes the ability to add charts generated from multiple defined metrics like team velocity or release statistics. More importantly, backlog management tools and boards -- task or kanban -- can be built and are straightforward to use. There isn't a need for secondary tools; development teams can build everything with TFS.
One tip on using TFS for kanban or sprint task boards -- create a single board. Many teams tend to create both a backlog board as well as a task board. However, two boards make updating more time-consuming, albeit not by much. The largest problem is that two boards introduce confusion. What do I update first? Which board is in control? The team's status may be misunderstood if someone doesn't keep both boards up to date in the correct order. Eliminate the unnecessary duplication of work and confusion and build a single board. In my opinion, one single kanban task board is the most direct, least error-prone method when creating task boards in TFS.
Test development and execution
TFS includes Microsoft Test Manager (MTM), but MTM is not actually needed: Teams can opt to do everything in TFS itself. However, MTM does have several features that make writing and editing tests in MTM less tedious than in TFS. For example, users can copy and paste test steps between tests in MTM directly without changing views. Editing tests in TFS requires patience because many Windows commands aren't available without digging. Additionally, when writing a test case within MTM, users can hit ALT + <Enter> to add multiple lines to a test step. In TFS, steps are created individually without the ability to add visual formatting. Adding visual formatting to test cases in the form of a bulleted list, numbered list or other formatting that breaks up the text helps improves readability. Testers can easily get lost in long tests of single sentences. Breaking long stretches of sentences with visual formatting is simply kinder and tester friendly.
Personally, I prefer the MTM user interface because I like to write tests directly into a single tool rather than importing or exporting from applications such as Word or Excel. It's a preference, but the nicer editing features make using MTM both faster and better than using TFS directly.
For executing tests, TFS and MTM work the same. The best part is that a tester can plan and test in the same place, simply using toolbar commands. In other words, it's optional to create separate test labs and then search and drag tests into execution suites. I can build my test suite on the fly in TFS and execute it directly, giving me additional time to actually test rather than create separate execution suites. I can still create full traceability and reporting metrics without taking extra steps leaving me more time for focused testing.
Microsoft, ATT introduce joint mobile office suite
Discover how to attain Inbox Zero using an MS tool
Read more about Microsoft's big data strategy
Does Microsoft TFS meet your QA and testing needs?
Dig Deeper on Topics Archive
Related Q&A from Amy Reichert
QA needs to reiterate its value to the business side of the organization. Use this tried-and-true advice to leverage documentation and automation to ... Continue Reading
Vendors have inched toward automated application testing for a long time, yet there is still room for growth. Software tester Amy Reichert offers her... Continue Reading
Whether you want to discover new software testing methodologies or rejuvenate test cases, QA is all about efficiency. Evaluate these testing ... Continue Reading