nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

The solution implemented uses the already-existing (in 2.6) /work
option, which allows the user to specify the directory to be used for
all output files, including TestResult.xml. Users may set this option
using a script so that it includes the date and time in any desired
format. If the option is not used, the current directory is the work
directory.

Access to this path from tests is now provided using
TestContext.WorkDirectory.

** Changed in: nunitv2
       Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/697069

Title:
  Feature request: dynamic location for TestResult.xml

Status in NUnit V2 Test Framework:
  Fix Committed

Bug description:
  Feature Request: provide an option to include the run date and time
  somewhere in the full path for the NUnit result file, TestResult.xml.
  Ideally, that path would either originate in a test fixture, or else
  originate in the NUnit framework, and be made available to the tests
  in a test fixture, so they could send output to the same directory.

  To illustrate the request with a specific example: suppose all tests
  in a test fixture output diagnostic information to a directory named
  "test run <run-date-time>", where "<run-date-time>" is the date and
  time of the construction of the test fixture at run time.  The purpose
  of this request is to provide some way to output the NUnit result file
  TestResult.xml to the same directory.

  Possible mechanisms to provide this feature, or something equivalent:

  1. Allow a TestFixture (or other class or method) to specify the
  output path for TestResult.xml.

  2. Provide for a  macro in NUnit's configurable output path for
  TestResult.xml, such that the date and time are included in the path,
  and make that path available to test fixtures and tests.

  3. Provide a post-processing step after TestResult.xml has been
  written, where a named batch file could be run.  Code in a test or
  test fixture could dynamically generate the contents of that file, ex.
  copy TestResult.xml "test run 2011-01-03-2300".

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunitv2/+bug/697069/+subscriptions