At Tech Days in Montreal a gentleman and I were chatting about Test Manager. He made a statement that I thought was well worth sharing.
It goes something like this:
“With Test Manager we no longer have to try and figure out when a tester leaves the company what all the excel spreadsheets on their desktop are all about. We know where the test cases are and what they test. It is great.”
I for one have been an advocate of reducing the paperwork tester’s have been required to generate. I know there were times we spent more time documenting what we were going to do then actually doing it. Including testing!
The comment was well stated and I agree Microsoft has created a great tool.
Free tool available for exporting your test cases to excel in a nicely formatted fashion.
Click to download here
You connect to Team Foundation Server by clicking the Connect TFS button.
Pick the Team Project you want to work with as shown below.
The test plans and test suites associated to the team project you selected display.
Pick a test plan and test suite then specify where you want to save the excel file to on your system and a name for the excel file.
Here is an example of test cases export to excel. The Actual Results, Pass/Fail and Comments are not populated from Test Manager. These would be fields your tester’s would enter as they are testing! Or you could remove them and add your own columns using this for test case reviews or any other type of reporting required.
It was a great evening for ObjectSharp Consulting last night. At the Microsoft Impact awards ObjectSharp partners Dave Lloyd, Barry Gervin and Mike Green accepted the
Partner of the Year award for Application Lifecycle Management.
Congratulations to Objectsharp and the Sharpe's.
The test case work item has a tab that lists the requirements/user stories that the test case tests. However, bugs related to the test case are not part of the listing. Dave has come up with a customization that changes the test case tab to include bugs created against the test case. With this customization you will see all work items that the test case tests.
Read Dave’s blog for more details and how to do the customization.
Shubhra Maji has posted two blogs on Coded UI test extension for 3rd party controls. Below are links to both blogs that are very informative and a must to read.
Windows Forms Controls – How to?
The Test Case Work item has a tab that lists Tested Requirements or User Stories (depending on the canned process template CMMI or Agile) that this Test Case tests.
When a bug is found you should write a test case so everyone knows how to validate that Bug once it’s fixed. Therefore why have a tab that just shows Tested Requirements/User Stories.
Lets use the Agile template as an example. The Tested User Stories tab will only allow you to add User Stories. Even though you could add a Bug with the tests relationship under All Links if you wanted.
It’s very easy to change this tabs behaviour to allow for Bugs also. Here’s how.
Open up the Test Case in the WIT editor that comes with the TFS 2010 Power Tools. Under the Layout tab find the TabGroup > TabPage – Tested User Stories > Control – User Stories tested by this Test Case and select it.
Select the Control Settings property and click on the ellipsis button. Leave Work Item Type Filters as Include. However in the drop down list to the right of that change it to also include Bug, then click OK,
Now change the Label from User Stories tested by this Test Case to something more appropriate like Tested by this Test Case.
Then switch focus to the Tab Page and change it’s label to something more appropriate like Tested User Stories and Bugs or just Tests.
Save the work item type.
You should now be able to select Bug as a work item type tested by this test case.
If you do not have a profile on LinkedIn it is time to join. There are amazing groups that are sharing information, posting questions & getting answers for a lot of different topics.
On the Visual Studio ALM User Group Anna shared a blog she posted “How to integration TFS and QTP”
Other LinkedIn groups related to TFS are:
- Visual Studi0 2010 Testing
- Microsoft Visual Studio ALM + Team Foundation Server (Team System)
- Microsoft TFS/VST Customization Experts
- Microsoft Testing Visual Studio 2010
- Microsoft Coded UI
There are also Agile groups:
- Agile Testing
- Agile Toronto
This in no way is a compete list.
Anutthara is the Program Manager in the Visual Studio ALM Test Tools group at Microsoft. She is doing a series blog on Exploratory Testing. Anu's team does exploratory testing on all their projects and is well versed on the topic. Follow Anu's Exploratory Testing series by clicking here.
I am doing a webcast today on the subject Quality Assurance in Mixed Technology Environments.
This is one in a series of Web Casts MS and partners like us are doing leading up to the TesTrek conference in Toronto. Where Deb Forsyth and I will be leading a workshop on Experience and Overcome the Challenges of Exploratory Testing.
It is amazing what a twit can do. Back in June 2011 Heather Payne twitted about a group of ladies in California that get together to learn how to code. The response was unbelievable. The first meeting to just talk about the idea rallied 85 people. The first session in Sept was sold out. The Ladies are learning how to code from scratch, no experience necessary by volunteers will to spend time training.
Did you know there is a 12% to 88% mix of women to men in the IT industry?
Ladies Learning Code website