Microsoft Completed Build Deletion – where has our test results gone?

Did you know that the files and data that are part of a completed build can delete?

Did you know that the data deleted cannot be recovered?

Did you know by default Test Results from any automated tests run against the build are deleted by default?

If you have the right permissions you can right-click in Build Explorer on a completed build and select delete. When you do that by default all the items associated with that completed build are deleted.

·         Details: Information about the completed build that is displayed in Build Explorer. This information includes build steps, requestor, and date and time queued.

·         Drop: File and folders output by the build and copied to the drop location.

·         Test Results: Results of any automated tests executed during the build process or results of any test published against this build.

·         Label: The version control marker associated with the specific file versions used by the build process.

·         Symbols: The debugging symbols published to a symbol server during the build.

You can also configure the retention policy and set auto deletion rules . Nothing wrong with that however is the person responsible for the “Build” setup and maintenance deleting could be deleting Test Results?

There is an option that can be set to stop the deletion of your Test Results. 

Make sure your teams understands what happens when deleting completed builds. Set that option to keep your test results, unless you don’t want them!


Testa Smile

Agile, Scrum webcasts to join has some create webcasts on subjects concerning Agile, Scrum. You can either sign up to them or go to the archive listing. Couple of interest are:

Agile Practices in a Traditional Organization

Adopting Test-First Development

Release Duration and Enterprise Agility

On May 15th is Agile and Quality: It is not an Oxymoron but a Necessity

Click here to check out the public webcast series.

Testa Smile

Code Coverage for Manual Testing is coming in vNext …

Microsoft is storyboarding the process of code coverage for manual testing. They are also looking for you to complete a quick survey on the subject. The Visual Studio ALM team are asking for our help so let’s give it to them. Click below to do the survey.

Code Coverage for Manual Testing Survey

This is how tools get made that we will use, thanks for helping.

Testa Smile

Microsoft MSDN Forum Gadget

If you are interested in following any of the MSDN Forum’s there is a gadget you can download that makes access to your favourite threads quick and simple.

Download here.

Testa [:)]

ALM User Group in Toronto meets May 24th

It is Methodology May at the TALMUG

Methodology. In the world of software development there are not many words that raise contention quite as quickly as this. But why is that? What are the differences between Agile, Iterative, and Rigorous software development methodologies? There has been buzz about Scrum, XP, Lean, Waterfall, Kanban, and RUP for years; how do they fit into this discussion? But most importantly, why should you care? What does the test team think of all this?

In Methodology May the TALMUG brings you a panel of ALM professionals to discuss and debate these very questions and maybe help you see what methodology could work best at your company.

Pizza and Pop will be available at 5:30pm - Come out and join in on the discussions.

Being held at 40 University, Suite 1301, Toronto meeting starts at 6pm.

Follow on twitter @TOALMUG

Click here to Sign Up 

Testa Smile

Microsoft seeing work item history made easier

Dave Lloyd has updated GetHistory a power tool for displaying work item history. Now you can export the work item history to excel. If your company has a audit process that has to be followed this tool may help you report on changes to requirements, test cases, bugs in just a few steps.

Click Get History to get the newest version. Keep your eye out on this tool you never know what features Dave may add!

Testa Smile

Toronto VS ALM User Group kick off meeting April 12th

The first Toronto VS ALM User Group kick off meeting is being held on April 12th @6:30pm sign up at TALMUG to get the details and register.

The User Group is for all roles within the Application Life Management team. Topics presented will vary from generic ALM practices to ALM with Visual Studio. If your involved in product management, a stakeholder, a business analysis or product owner, a developer or a tester this User Group is for you.

The goal of the first meeting will be to:

  • Define the group’s mission
  • Select an appropriate name
  • Document the roles of the executive
  • Recruit volunteers
  • Funding
  • Discuss how to reach out for sponsors
  • Discuss meeting locations
  • Discuss ideas for the first few meeting topics

Come out on April 12th and help us to kick-off this new user group code named TALMUG.

Testa Smile

Microsoft Impact award given to ObjectSharp

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.

Testa Smile

Microsoft TFS and QTP integration

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.

Testa Smile