Visual Studio Architecture Guidance - Use UML Models for Testing
To promote our ranger work a bit more… I want to high light a specific scenario… create tests from UML models. I already played with this scenario from an automation perspective 2 years ago, when VS2010 was still in CTP. [see the bad quality video, already watched more as 17.000 time 
]
Anyway, there are two common test design techniques that are used to specify test cases based on UML. The first is the Process cycle test[1] (PCT) which uses UML activity diagrams. The other one is Use Case Test[2] (UCT) which is based on Use Case diagrams.
Still on my backlog to make a fully working automation for these [waiting for Feature Builder to go RTM]. But, you also can do it manually, as you can see in the hands-on-labs.
Task 1: Open Activity Diagram
Task 2: Create logical test cases based on PCT
-
· Path combinations for decision point 1: (1,2) and (1,3);
-
· Path combinations for decision point 2: (2,4) and (3,4);
Based on PCT path combinations for test measure 2 are 1-2-4 and 1-3-4 for these paths test cases should be created.
… and create these TestCases in Microsoft Test Manager
Still a great ALM scenario where the different rolls in the lifecycle use artifacts from each other from that central repository.
[first time use of the wave 4 live writer, still like it…]
Visual Studio 2010 Team Foundation Server Requirements Management Guidance
Another delivery from the VS ALM Rangers is public available… the Requirements Management Guidance.
Very useful guidance, with a small contribution from me with the Enrich VSTA 2010 Use case diagram with SketchFlow Screens post. [see the Requirements Elicitation part].
