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
If your looking for a way to create
test configurations that can be used in all your team projects check out Dave Lloyds blog. Dave explains how to edit the process
template to add or change test configurations.
I’m sure you have noticed that when you create a new TFS project in 2010 there are a couple of default Test Configurations created.
Operating System - Windows 7
Browser – Internet Explorer 8.0
Like most people you will go into Test Manager and add the configurations you really need. Then you create another project and those default configurations are back. Unfortunately there is no way in the UI to add the configurations you added in the first project to other projects. Not without writing some code.
However if you look at the process template those defaults are in there, however they are not made available for edit through the Process editor UI.
Of course you can edit the file, and add your Test Configurations manually. The file you are looking for is testconfiguration.xml and it can be found in the Test Management folder of the downloaded process template.
<?xml version="1.0" encoding="utf-8" ?>
<TestConfiguration name="Windows 7 and IE 8"
description="Default operating system and browser for testing" state="active" isdefault="true">
name="Operating System" value="Windows 7" />
name="Browser" value="Internet Explorer 8.0" />
If you want to add test configurations to a new project edit this file in your process template first. The defaults you put in here will be created in your new project.
Recently, I have been getting a lot of questions about what are the things we should consider before upgrading to SharePoint 2010. Here is my list:
- Ensure your environment is fully functioning before you perform an upgrade. No need to carry over any old issues into your new SharePoint 2010 environment
- Make sure you meet hardware requirements: 64-bit hardware, 4 cores CPU or better, 8Gb of RAM or better, enough disk storage, et cetera.
- Make sure you meet software requirements Windows Server 2008 SP2 or better, SQL Server 2005 SP3 or better, SharePoint prerequisites installed, member of Active Directory domain, and so on. Everything must be 64 bit.
- Plan browser support (IE6 is not supported) and Office client upgrade
- Get all your SharePoint servers to Service Pack 2 or later
- Run Pre-Upgrade check to identify potential issues that will prevent us from successfully upgrading to SharePoint 2010. Review the report. Fix the errors. Re-run pre-upgrade check utility. Repeat, if needed.
- Identify all customizations such as 3rd party webparts or look-n-feel changes. Make sure those will work properly in SharePoint 2010
- Backup all SharePoint databases. Seriously. Backup all SharePoint databases.
- Choose upgrade approach: in-place approach or database attach upgrade. Or hybrid approach.
- Test the upgrade process. Before you perform an upgrade in production environment, test the upgrade process and address any issues you found during testing
- UPGRADE all your SharePoint servers to SharePoint 2010 (finally)
- Evaluate the upgrade. Review logs, check update status troubleshoot issues and errors.
- Use Visual Upgrade to convert site collections to the SharePoint 2010 product look
- Completing the upgrade: configure service applications, update database permissions, configure authentication, validate the upgrade, etc.
- Enjoy the SharePoint 2010 awesomeness.
To learn more about how to build a sound SharePoint environment, check out our Upcoming Courses
Sam Guckenheimer is the Product Owner of Microsoft Visual Studio product line. He has 30 years' experience as architect, developer, tester, product manager, project manager and general manager in the software industry worldwide.
Sam’s new book “Agile Software Engineering with Visual Studio: From Concept to Continuous Feedback” is a must for all to read. Available in paperback and kindle from Amazon.
Sam recently did a webcast for TesTrek 2011 in Toronto which is also well worth watching. Sam talks about Getting Agile with Testing.
“Testing is central to the success or failure of any organization adopting the Agile Consensus. A modern testing approach can be a great enabler of value flow, transparency and the reduction of waste. An outmoded testing approach can be a huge impediment and source of unending conflict. As testers, it's important that we be on the right side of the consensus and be the enablers. The alternative is untenable. In this session, we will explore fundamental principles of agile project delivery and discuss the impact on the QA lifecycle. “
If your in Toronto the week of November 7th sign up for TesTrek 2011 Conference where Sam is the keynote speaker. Dave Lloyd and I will be doing a hands on workshop on Exploratory Testing. There is lots happening this year at TesTrek check it out.