Pex - Release Notes

64 bit Support
Pex can be installed on X64 machine but runs 32-bit processes only (Wow64).

UI Changes
Mostly moving around buttons, changing labels, and adding more icons.
In particular, the infamous red bar has been integrated into a friendly yellow bar.

New features
Code-update preview dialog.
New quick actions for generated tests: Debug, Send To... Mail, Text-file, Clipboard.

Testability
Pex flags Testability issues.

Fixed bugs and other changes
Generated code quality: prettier method names, prettier local names.
Lots of other bug fixes.

FatalExecutionEngineError (-2146233082), or StackOverflow (-2147023895)
This error might occur shortly after you invoke Pex, either from the command-line or Visual Studio. This is a known bug, and caused by a race condition in Pex. Usually, when you simply invoke Pex again, it will work just fine.

WPF issue: API restriction: '...WindowsBase.dll' has already loaded from a different location Pex may break your WPF applications. If you experience this issue, please uninstall Pex from the machine. We are working towards a fix for this issue.

First update of Pex!

Fixed bugs and other changes
- Pex now complains gracefully when other profilers are active, e.g. certain mock frameworks.
- The dynamic coverage view is no longer shown by default in Visual Studio, but it must be enabled (if desired) in the 'Tools' / 'Options' menu.

Visual Studio 2005 users
Visual Studio 2008 Standard (or higher) is required to run the samples and use the Visual Studio Add-in. If you have Visual Studio 2005 or Visual Studio 2008 *Express*, you can still use Pex from the command line. See the tutorial or the command line reference.

Pex Wizard in Visual Studio may be slow
When using the Pex Wizard in Visual Studio, devenv.exe might fully utilize a CPU for a long time. We will work on a fix for this issue in the next release. A workaround is to use the wizard from the command line and using the /testp flag.

First release of Pex!

ClrMonitorFail (-667) This error might be result of an interaction of Pex with another installed Visual Add-in that also acts as a profiler, e.g. certain mock frameworks. This issue will be fixed in the next release. As a workaround, try to uninstall other Add-ins.

When the Pex Wizard generates parameterized unit test stubs, it inserts by default a call to Assert.Inconclusive(). This method throws a special exception that tells Pex (and MSTest) that the test is inconclusive.
This mechanism forces the tester to review and validate each generated parameterized unit test by removing the Assert.Inconclusive() call.
To suppress generating Assert.Inconclusive() calls in Visual Studio, go to the 'Tools' / 'Options' menu. Then select the 'Pex' / 'Wizard' pane and disable 'Make generated test inconclusive by default'.