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

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