Skip to main content

Testing for Continuous Delivery

The Microsoft Patterns & Practices team released a new document about ‘Testing for Continuous Delivery with Visual Studio 2012 RC’.

“This guide describes how testing has been changing over the years and how the testing infrastructure you can build with Visual Studio 2012 RC will help you achieve continuous delivery of your software projects. This guide provides an end-to-end walkthrough of the testing scenarios supported by the Visual Studio 2012 RC infrastructure. It will help testers and developers use Team Foundation Server effectively as an application lifecycle management solution for testing and supporting products.

This guide helps you

  • Understand how testing is changing with the new tools available to testers.
  • Set up the testing infrastructure.
  • Use the tools for unit testing.
  • Understand how the lab environment works and how it supports a project.
  • Understand the power of the manual testing tools.
  • Learn to use the tools for automated testing.
  • Use the tools in the testing toolbox.

In addition, this guidance describes testing with the Visual Studio 2012 RC testing infrastructure composed of Team Foundation Server, Build System, Test Controller, and SharePoint, and discusses the supported reporting functionality that can help track various test velocities and code coverage. This guide also helps you understand the critical ways in which your testing processes will change with the use of these new tools.

After reading this book, you will be familiar with how to set up Team Foundation Server in Visual Studio 2012 RC and its corresponding infrastructure components in a number of configurations. You'll also have a good understanding of how to use the Visual Studio 2012 RC testing tools such as Lab Manager and code coverage tests to achieve a far more effective testing experience and full application lifecycle management for your system.”

The related code samples can be downloaded from Codeplex.

ALM Maturity

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more