Azure DevOps Staged execution of tests in Azure DevOps Pipelines When running Unit Tests in your build system, you may want to first run the most important suite, the one that should never fail, the ones that are currently being changed, finally the regression suite that may be slower to execute.
Azure DevOps Enable parallel execution of tests using the Visual Studio Test Runner 2015.1 Does your machine have multiple CPU's or cores? Are your tests truly independent and thread safe? In that case you'll be able to speed up your test runs considerably by enabling multi-threaded support to the Visual Studio Test Runner. This works in both Visual Studio as
XAML Build Staged execution of unit tests on Team Build > Using Team Foundation Sever 2015 or newer or are you on Azure DevOps? Find updated guidance here [https://jessehouwing.net/staged-execution-of-tests-in-azure-devops-pipelines/]! When running Unit Tests in your build system, you may want to first run the most important suite, the one that should never fail, the ones that are
Visual Studio 2013 Resolving test run issues in Visual Studio "Some or all identity references could not be translated" One of my devs ran into a strange bug in the Visual Studio test runner today. It manifests itself in the fact that tests won't run and you'll find the following error message in the Output\Test window: ------ Run test started ------ Some or all
Visual Studio Extensions Enabling Mighty Moose for Visual Studio 2013 Warning: This is probably totally unsupported, and might come with its own class of issues, but so far it seems to work... To enable Mighty Moose in Visual Studio 2013 do the following steps: 1. Install Mighty Moose 2. Create a 2013 Addin file 3. Copy theC:\Program Files (x86)
Visual Studio 2012 First ALM Ranger guidance in Ebook format By based on a Visual Studio User Voicerequest [http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2639467-make-alm-ranger-guides-available-on-msdn-and-ebook] and a lot of internal discussions we, the ALM Rangers, are proud to present our very first official ebook formatted guidance [http://blogs.msdn.com/b/willy-peter_schaub/archive/2013/05/29/better-unit-testing-with-microsoft-fakes-guide-a-la-mobi-and-epub.aspx?
CodedUI Testing Creating a Custom Unit Test Generator Provider Plugin for Specflow 1.9 After getting CodedUI Code First and Specflow to play nicely together in the past week, we ran into a few issues with the distribution of the Custom Code Generator Provider assembly to all team members. The SpecFlow binaries installed under a path that contains a random character string and I
Static Analysis Combining CodedUI Code first, SpecFlow and Visual Studio 2012 Today we tried to combine a number of different test technologies on the latest version of Visual Studio and ran into a few small issues. We found a work around for all of them. So if you want to use the BDD style of Specflow to test the UI of
Code Review Techdays 2013 presentation - Better code through review and tools By request of the audience, a link to the slide deck of our Techdays 2013 presentation on Better code through review and tools [http://www.microsoft.com/netherlands/techdays/SessionDetail.aspx?sessionId=3780] (in Dutch). There isn't too much useful information in the deck itself, since Thomas Huijer
Agile Bring back the "Create Unit Tests" feature from Visual Studio 2010? There's a feature request on User Voice that requests Microsoft to bring back the "Create Unit Test" menu item which was removed in Visual Studio 2012 [http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2748862-add-create-unit-tests-menu-option-back-] . I've seen it come up as a potential Ranger solution
XAML Build Funny issue with Code Coverage and Reflection Just stumbled upon a tricky change which happens to your assemblies when you're running your tests with Code Coverage enabled. Take the following piece of code: var types = typeof(Program).Assembly.GetExportedTypes(); foreach (Type t in types) { // ... } In our case the behavior of the code under test changed
Team Foundation Server Things that make your unit tests unreliable Over the past few months I've come across a lot of Unit Tests that triggered all kinds of crazy corner cases inside mstest. The most interesting observation is that the behavior inside Visual Studio is often different (or doesn't occur) than in Team Build when this
