Loading ...
Sorry, an error occurred while loading the content.
 

Ann: NUnit 2.5.4 Released

Expand Messages
  • charlie poole
    Hi All, NUnit 2.5.4 is now available at http://launchpad.net/nunitv2. See the release notes below. Charlie Features * NUnit now defaults to running an assembly
    Message 1 of 1 , Apr 8, 2010
      Hi All,

      NUnit 2.5.4 is now available at http://launchpad.net/nunitv2. See the
      release notes below.

      Charlie

      Features

      * NUnit now defaults to running an assembly under the runtime
      version for which it was built. If that version is not available, a
      higher version may be used. See the Runtime Selection page for
      details.
      * ProjectEditor now provides a 'Default' selection for the runtime
      version to be used.
      * The XML result file format has been enhanced to provide
      additional information needed to identify and report on theories and
      also includes extended result states such as Inconclusive, Invalid,
      Error and Cancelled.
      * The EmptyConstraint (Is.Empty) may now be used with a
      DirectoryInfo to test whether the directory is empty.
      * Datapoints for boolean and enum arguments are now generated
      automatically for theories.
      * The cache path for shadow copying is now saved in the NUnit
      settings file rather than in the config files. The settings dialog may
      be used to change it if necessary.

      Bug Fixes

      * NUnit crashing when a message contains ']]>'
      * Replace compile-time exclusion of code from Mono with run-time test
      * Message associated with Assert.Inconclusive() not shown in XML
      * Category on test case clashes with category on the test method
      * Console crash when specifying /domain:Single with multiple assemblies
      * Incorrect relative path causing problems in saving projects
      * Message associated with Assert.Pass() not shown in XML
      * Tests with ExpectedException compiled against NUnit 2.4 always
      pass under 2.5
      * Datapoints with a null value were not being passed correctly to
      theories
      * Error in XML output with FSharp.Net
      * Documentation refers to files missing from Windows install
      * Parameterized test fixtures with null parameters not handled correctly
      * Theories now work as designed, failing when no data satisfies
      the assumptions
      * Target framework of net-3.5 was causing console to crash
      * Mono stack traces are now parsed correctly in the Gui
      * Test failures under .NET 1.1
      * Thread CurentPrincipal set in TestFixtureSetUp not maintained
      between tests


      [Non-text portions of this message have been removed]
    Your message has been successfully submitted and would be delivered to recipients shortly.