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.
VS2010 TMap Testing Template | Initial Work Items #1
During the unfolding of the TMap for VS2010 process template, several pre-defined work items are created for the test organization. These work items helps the test organization to start structured test process with a Master Test Plan.
When starting a testing effort first several things needs to be in place… we need to understand the assignment, determine what we are going to test what are the risks, etc… the first four steps in the image below.
Beside these steps also decisions needs to be taken about what to test where, you don’t want to loose money by testing things twice. As described in the TMap Next book:
The type of system and/or development approach and/or test policy determine which forms of which test levels are best used. For iterative system development, for instance, a thorough acceptance test is less obvious. This is because the quality from the user perspective has already been tested in previous test levels. However, for package implementations there is a far greater emphasis on a thorough acceptance test. The risks here are focused on the implementation of the package in the organization, a typical acceptance test aspect.
So, topics covered by the master test plan can be:
All these activities are described in detail in the TMap Next book, and you also get these steps when using the TMap for VS2010 process template, as initial work items.
These Master Test Plan activities got descriptive guidance attached to it. Accessible by using Microsoft Test Manager 2010, Visual Studio 2010 or the TFS 2010 Web Access tool, helping every role, to understand the assignment, the activities and test goals.
[Microsoft Test Manager 2010 | Initial Master Test Plan Work Items with guidance]
[Visual Studio 2010 | Initial Master Test Plan Work Items with guidance]
[ TFS 2010 Web Access | Initial Master Test Plan Work Items with guidance]
So, when the project starts the guy / girl with the Test Manager role has to assign the different tasks to the right team members to complete the Master Test Plan.
In a following post [probably not the next one] some Word and Excel templates which support these tasks and can be found at the project portal. First a planned post about initial work items for planning the infrastructure.
If you want to keep up to date about TMap testing and the VS2010 process template, send me an email with your name and organization
. Beside this blog and our the TMap codeplex site we have a community of users, to exchange ideas, usages stories and additional updates of the template en testing practices.
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.
Microsoft Test and Lab Manager and security and permission settings
Within TFS you can set permissions, what people are aloud to do within projects and with 2010 in place also within project collections and within Microsoft Test and Lab Manager.
In some situations, project settings, you want to set these permissions. For example in the TMap process template there are different rolls responsible for different tasks. The Test Manager is responsible for the Master test plan, the Test infrastructure coordinator for the test infrastructure and tools, the test coordinator for the test plans, the runs and reports and the tester for creating and execution of the tests cases.
These rolls/ groups you also can find in the TMap Process Template.
All rolls have there specific restrictions. For example a Test Infrastructure Coordinator is aloud to setup lab environments but a Tester isn’t, and a test coordinator can create a test plan but a tester isn’t. A test manager and coordinator can edit test runs results. A tester can execute test cases but a developer can’t, a developer can change sources but a tester can’t… etc, etc… A frequent ask question by test organizations is: how can a set this restrictions…. the answer is it is easy but you need to have project edit permissions :-)
On several places you can set security permissions.
In the Team Foundation Admin Console, the same settings can be set within Visual Studio menu Team—> Team Project Collections Setting
You only can set project collection and TFS specific setting at this level, not that interesting for test management.
Within Visual Studio, right mouse click on within Team Explorer or by using the Team menu.
This is a more interesting place to set permissions for the test organization. For example in this setting a test coordinator is aloud to create test runs, but can’t change configurations and environments.
This results in the fact that he must contact the test infrastructure coordinator to maintain the test infrastructure. And he got a message when he tries to change a setting in Lab Center.
A hidden security setting [I call it hidden because its hard to find in my opinion and I had to search for the projectplan permissions] is a the Area and Iteration menu item, just below the ‘Group Membership’ item.
When clicking the ‘Areas and Iteration’ menu item and click on the bottom right of the dialog what appears you can set permissions for the selected Area node or Iteration node. For the test organization important manage test plan permissions can be set.
When you set this permission so a tester isn’t aloud to manage test plans he gets nice an clean messages when he tries to save one.
But, it gets even more interesting. When a tester isn’t aloud to manage test plans he also can’t add test cases to a test plan. So, the create new test case in the plan tab of MTLM also will result in a ‘Not Aloud Message’. While the tester is aloud to create test cases he isn’t aloud to add them to a test plan, within MTLM he has to create test cases in the ‘organize’ tab –> test case manager. So a test coordinator, or some one else who has the manage test plan permission can add it to the test plan.
I have spoken with test organizations who prefer this way of restrictions also have spoken with who don’t want this. Within the TMap Process Template, you will find a light weight implementation of these permissions settings. [not yet in the download ]
To mention all the permission settings locations, right click on the source control treeview and select properties, you can set permissions for source control in that dialog [ you also have to maintain the reporting server and the SharePoint server separately]. ping me if I forgot a security settings location…
VSTS 2010 TMap process templates infographic
Been playing a bit with the creation of infograpics, this is one I created about VSTS 2010 and TMap, what are the benifits of using them together and how are they connected.
This one isn’t finisched / approved yet (so not donwloadable in full format:-), need to change the screenshots and text in several places. But, the idea is to have them printed on a placemat with on the back contact information and to make notes.
VSTS 2010 Test Edition at the TMap® Dag 2009 [Dutch]
Theorie en praktijk wisselen elkaar af met onderwerpen als TMap NEXT®, ketentesten, security testen, Agile testen en nog veel meer actuele onderwerpen.
Tijdens de TMap® Dag 2009 wordt het nieuwe boek TPI® NEXT gelanceerd! Een compleet herziene versie van het TPI® model waarin voor het eerst de business doelen écht een ssentiële rol spelen.
WS8 -- De TMap NEXT® Proces template voor Visual Studio Team System
Gerard van der Pol, Microsoft
Visual Studio Team System ondersteunt uw procesbenadering voor software ontwikkeling door het gebruik van Proces Templates. De guidance en werkwijze kunnen hierdoor transparant worden ondersteund door de in het project gebruikte tooling. Voor de nieuwe 2010 release
van Visual Studio Team System is er een proces template in de maak rondom TMap NEXT®.
Deze sessie introduceert de TMap NEXT® proces template en laat zien welke voordelen er te verwachten zijn door deze te hanteren. Tevens zullen we laten zien op welke wijze de template aansluit op de bestaande en nieuwe test functionaliteit in Team System.
Programma [pdf]
Datum: 17 november 2009
Locatie: Hotel van der Valk, Vianen
Aanmelden: www.sogeti.nl