Presentation: TMap for VS2010, Testing Practices with ALM tools
My deck and demo’s for TMap® meets Visual Studio®, München.
One funny thing I didn’t know, in Germany they knock on the table instead off clapping...
the Deck [from SlideShare]
The 5 demo’s [from YouTube]
Demo 1 for TMap for VS2010 (Munchen) presentation, Upload TMap Process Template and create a new project. | Demo 2 for TMap for VS2010 (Munchen) presentation, Edit the TMap Process Template with TFS powertool Process Editor. |
Demo 3 for TMap for VS2010 (Munchen) presentation,Test Case Writing with a focus on shared steps, validations and parameters | Demo 4 for TMap for VS2010 (Munchen) presentation, Run the in demo 3 created test cases. focus on shared step, validations and parameters |
Demo 5 for TMap for VS2010 (Munchen) presentation, Create a codedUI test from the in demo 3 created test cases. Focus on shared step, parameters and validation/ assertion | |
and two pictures.
 |  |
| My German colleagues explaining TMap… | Had the most scary flight home ever… it was a rollercoaster. |
video: 101 bug dev test collaboration scenario…
Second 101 demo, a basic developer test collaboration scenario.
thx for watching… see TMap.Codeplex.com for more details
Sogeti TMAP process template certified and ready
cross post from Mattias Sköld.
Today we finalized the RTM version of our TMAP process template and it will soon be available for free download from the official TMAP.Net site (direct link to download http://eng.tmap.net/Home/archief/957794.jsp).
Certified process template
Sogeti's TMAP template has as the first template passed the new Visual Studio Certified Process Templates Program announced by Microsoft and can therefore use the new Certified process template logo. If you want to know more about the certification program Stephanie Saad Cuthbertson has a post on the details.
TMAP.codeplex.com
The TMAP template will continue to develop and improve on codeplex. You will still find the latest bits and contribute on the future directions of the TMAP process template by filing feedback and suggestions at tmap.codeplex.com.
Doug Seven: Improving Developer-Tester Collaboration with Microsoft Visual Studio 2010
Watch it here: http://ch9.ms/BMRW
With Sogeti on top of the partner list with our TMap Testing Process Template…
TMap for VS2010 Flyer
English version [pdf]
Dutch version [pdf]
TMap for VS2010 Process Template Explained…
Recorded a LiveMeeting yesterday about the TMap for VS2010 Testing Process Template.
Click to watch it [ 53:08 ]
VS2010 TMap Testing Template | The Test Infrastructure
Initial Work Items #2 Setting up and maintaining the test infrastructure, beside the Initial Work Items #1 which describe / help create the Master Test Plan, also activities for setting up the environment must take place at the early stage of the project.
The test infrastructure consists of the facilities and resources necessary to carry out the testing satisfactorily. A distinction is made between the facilities for test execution (test environments), for supporting the testing (test tools) and for the day-to-day work of the testers (workplaces).
While it doesn’t look like rocket science, just setting up an environment, most projects lack a good structure for these activities resulting in time loose and poor quality.
The TMap for VS2010 process template helps with setting up the infrastructure by providing 6 initial work items, with specific guidance, discussing the TMap activities within VS2010 ,which covers Lab Management and Test Manager.
Together with the initial work items and the guidance also three checklists are added to help.
TMap for VS2010 Testing Process Template RC published on Codeplex.
A bit later as planned, due to my broken leg.
Just checked in the RC version of the TMap for VS2010 process template…
Downloaded it from TMap.Codeplex.com.
Still a lot of work to do, specially on the documentation and reporting part [lucky me, my colleagues from Sogeti US, Sweden and other Sogeti countries are helping me]. But still, the documentation section is a very good starting point when you want to discover the TMap processes for VS2010.
Later this week I will post some more content.
Speaking at Dutch DevDays and Danish ALM Day
Will be speaking at the Dutch DevDays [about VS2010 general/practical usages] and Danish ALM Day [about TMap for VS2010] in March/April.
The Hague, The Netherlands
March 30-31, 2010
DevDays 2010
[update]
Will give the interactive session "ALM Best Practices: Modeling the Showcase Application" with @Edwb (www.edwardbakker.nl) and the session "ALM Best Practices: Testing the Showcase Application" with www.RobKuijt.nl. Rob is a real tester, who will give an interesting look in the world of the tester.
Copenhagen, Denmark
April 9, 2010
ALM Day 2010
Not as much as Brian Keller [4 weeks, 7 countries, 25+ sessions, 1 suitcase…]… looking forward to it, specially because I can travel again and almost can walk without crutches. So, I can do my talks standing with my hands on the keyboard without falling.
Traceability in VS2010
Always an interesting question, how does traceability work in VS2010?
To often asked without any context, or only asked from a requirements perspective. Still way too open to answer in a tweet. So, a post to canalize those questions a little bit more…
[see the image below for the numbers]
you can take two directions when talking about traceability. The first is focused on “work”, the work items repository part of TFS [on the left side of the green dotted line]. with work related traceability we can answer questions like “did we completed all tasks for that requirement?” [for more see the red list]. Information which is very important for every roll in the Application Lifecycle. A tester want to know if he can start testing, so he want to see if the developer is ready. A project manager wants to plan the work. Developers want to know if designers are ready to start with a stabile set of needs… and many more. All work related information, and information which can be tracked/ traced by using work item and its repository.
VS2010 main capability for work related traceability are the TFS work item repository [see image below from MSDN] and linking of work items, setting up a hierarchy.
We can breakdown requirements, or user stories, in tasks. 
tasks that needs to be executed to get the requirement done. These tasks can have a parent-child relation [and other see Working with Link Types on MSDN]. Giving us the information we need in any kind of way, for example reports.
So far the work related traceability. The other kind of traceability is based on artifacts, things we make during the application lifecycle, I will call them ALM artifacts. ALM artifacts are used to create the solution/ application. For example the source, XAML and configuration files which make the solution. But, also the diagrams which we created to make a correct, consistent and good communicated application architecture, we use them to drill down from the needs to code. And also test cases belong to the things we make during the application lifecycle [I can imaging when you get confused now, test cases are within VS2010 work item types, but they definitely belong to the artifacts section].
Use case – user story what is the difference… I often use both [see this piece of MSDN documentation for modeling requirements]. User stories are work item types and use cases are ALM artifacts. So, they are a great bridge between the ‘work-world’ and ‘artifact-world’. The good thing is the capability of VS2010 to link diagrams, and other model elements to work items. [How to: Link Work Items to Model Elements], this give us the capability to create a trace.
From the description and diagrams of the requirements, the often called problem domain, we have to make a big jump into the solution domain.
Diagrams are created like the component diagram and layer diagrams visualizing the high level pieces of the solution with the dependency and interfaces between these components and layers. [used this image in this post; the modeling world].
It is also a big gap for traceability, to get this a little bit better a solution can be the replaying of scenarios written down in the user stories and drawn in activities as described in this post; VS2010 Modeling; Create Lifeline from Component.
A trace back from component/layer to requirement can be a link from model element to the user story work items in where he is used. Never did this, it’s a manual process and probably people will forget the links, maybe with some kind of notification this would be valuable…
An interesting VS2010 capability is the connection between the layer diagram and the sources. This makes a trace possible between the high level design and the sources. See image below.
Because test cases are work item types in VS2010 they can be connected to any other ALM artifact, giving us the possibility to connect for example test cases to use case diagrams. Easier to accomplish and to maintain is the connection with test tasks and corresponding user story. But this doesn’t answers questions like; “which code is touched by this test”. VS2010 answers this question with Test Impact, see “Determining Which Builds Have Bug Fixes, New Features, or Requirements”, “Recommending Tests to Run That are Affected by Code Changes” and “Developing Tests from a Model”.
Another interesting traceability scenario can be build with test case generation, see this ‘old’ Model Based Testing beta 1 video. [some more info on MBT can be read on Rob’s blog]
Next, 
all have a work related task. So, not only traceability within the two sections is possible also traceability between the two sections is possible. answering questions like; “which task created this line of code?”… creating this link / trace is a manual task but it can be controlled by a check-in policy.
So, when someone asks you the question; “what about traceability in VS2010?” you now can canalize this and guide him/ her to the real traceability question they want to have answered [and tell the solution]….
< probably more to come on this interesting topic, also because the extensibility model of the diagrams is powerful enough to create your own required traceability between artifacts with notifications and work item linking… very very interesting >