For re-use: https://github.com/rockpooldigital/bmx-testresultssummary Cheers again, Jamie

At the moment the MsTest extension requires a test file be specified. However, we do have the code public for this extension: https://github.com/inedo/bmx-mstest If you're interested modifying the extension quicker than we can, check out: http://inedo.com/support/tutorials/cloning-and-patching-an-inedo-extension As for email, that might require more customization. You can instead have users sign up for the "Execution Completed" notifier which will link them to the test results.

This appears to be a problem with the tests themselves. I would take a look at the Cleanup method and see what objects could possibly be null. This post (http://stackoverflow.com/a/10751484/44765) shows the some of the differences with running in the command line MsTest vs. Visual Studio.

We have a known issue where if you have two test actions with the same group name in the same deployment plan, you will get this error. The workaround is to use a different group name for each test action in the same plan.

I'm not sure what you mean by distributed tests for MSTest, but pointing the MSTest Action at the configuration file is the way to go if you already have one. As for the batch file problem, what does your action configuration look like to try to run the .bat file? Is it set to run on the correct server? Does the account running BuildMaster have access to those paths? It's also possible that when you're running locally on the target server that you have the MSTest directory in your PATH but the BuildMaster account doesn't. That being said, is there a problem running the MSTest action as opposed to this batch file? It will be better integrated into the logs if you use that instead - the batch output will only give you stdout/stderr as opposed to an individual test breakdown.

It looks like you're currently on 2.6. You'll need to upgrade to BuildMaster 3.0... we made a breaking change to the API/SDK and are no longer supporting our extensions written for 2.x.