Skip to main content

Exporting Microsoft Test Manager Test Results to Word

With the release of Visual Studio 2010 Microsoft introduced a new Visual Studio version called Microsoft Visual Studio Test Professional 2010. This version includes a tool called Microsoft Test Manager that is also a part of the Visual Studio 2010 Ultimate installation.

Although it is a really great tool that simplifies the work of the tester a lot, it still has some missing features. One of the areas where it lacks in functionality is reporting. There is no easy way to export the tests, test results, and so on in an easy to use format. Luckily there is a tool named Test Scribe  that allows you to see Test Plan, Test Results, Test Suites, Test Cases, Test Configurations, Test Settings in a Word document which you can also print out.

If you didn’t install it yet, go do that first.

Using Test Scribe

  • Open Microsoft Test Manager
  • Click on the Testing Center dropdown
  • A new option Tools is added to the drop down list. Select it.

testscribe1

  • Click on Test Plan Summary
  • Select/Highlight a Test Plan
  • Click on the Generate Button

testscribe2

  • The Test Plan document will display the following Test Plan details, Test Suite details, Test Case details, and Test Configuration details
Labels:

Popular posts from this blog

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

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

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