nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

Public bug reported:

Taken from a post to the nunit-discuss list by Patrick Simon...

Hello -

This post may be of interest to anyone who actually tries to build
NUnit 2.5.8 from the source files provided in the distribution file
NUnit-2.5.8.10295-src.zip.

The build requires a file NUnit-2.5.8.10295\src\NUnitCore\schemas
\Results.xsd, which was not included in the distribution.  Also, the
schemas directory itself does not appear in the source tree from the
distribution.  Actually the build technically succeeds without the
Results.xsd file, but 5 tests in NUnitCore\Tests\XmlTest.cs fail.
There is a file Results.xsd in the directory NUnit-2.5.8.10295\doc
\files, but that is not the one required for these tests.  Instead,
create the schemas directory and then create Results.xsd in that
directory using the contents of http://nunit.org/files/testresult_schema_25.txt.
That seems to be an updated version of the one in doc\files.  With
that in place, a clean release build for net-2.0 runs through all of
the tests in NUnitTests.nunit with no errors.

These build and test results were obtained using nant-0.90, net-2.0,
and MS VS 2008 on Windows XP, more or less starting with the
information on the page "How to Build NUnit from source using NAnt" on
the NUnit wiki.

- Pat

p.s. There is also a page entitled "How to Build NUnit from source
using Visual Studio", but the solution files mentioned on that page
are not in the source distribution.  I have partially constructed VS
solution files, enough to build some but not all of the NUnit
components.  In addition to the issues above, the
nunit.core.tests.csproj refers to DirectoryChangeTests.cs which does
not exist, and test-assembly.csproj referes to DirectoryChange
Fixture.cs, which also does not exist.  If you decide to go the route
of creating a solution file to wrap the various Visual Studio NUnit
project files, references to those files should be removed from their
respective csproj files.

** Affects: nunitv2
     Importance: Undecided
         Status: New

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

Title:
  NUnit 2.5.8 Build Problems

Status in NUnit V2 Test Framework:
  New

Bug description:
  Taken from a post to the nunit-discuss list by Patrick Simon...

Hello -

This post may be of interest to anyone who actually tries to build
NUnit 2.5.8 from the source files provided in the distribution file
NUnit-2.5.8.10295-src.zip.

The build requires a file NUnit-2.5.8.10295\src\NUnitCore\schemas
\Results.xsd, which was not included in the distribution.  Also, the
schemas directory itself does not appear in the source tree from the
distribution.  Actually the build technically succeeds without the
Results.xsd file, but 5 tests in NUnitCore\Tests\XmlTest.cs fail.
There is a file Results.xsd in the directory NUnit-2.5.8.10295\doc
\files, but that is not the one required for these tests.  Instead,
create the schemas directory and then create Results.xsd in that
directory using the contents of http://nunit.org/files/testresult_schema_25.txt.
That seems to be an updated version of the one in doc\files.  With
that in place, a clean release build for net-2.0 runs through all of
the tests in NUnitTests.nunit with no errors.

These build and test results were obtained using nant-0.90, net-2.0,
and MS VS 2008 on Windows XP, more or less starting with the
information on the page "How to Build NUnit from source using NAnt" on
the NUnit wiki.

- Pat

p.s. There is also a page entitled "How to Build NUnit from source
using Visual Studio", but the solution files mentioned on that page
are not in the source distribution.  I have partially constructed VS
solution files, enough to build some but not all of the NUnit
components.  In addition to the issues above, the
nunit.core.tests.csproj refers to DirectoryChangeTests.cs which does
not exist, and test-assembly.csproj referes to DirectoryChange
Fixture.cs, which also does not exist.  If you decide to go the route
of creating a solution file to wrap the various Visual Studio NUnit
project files, references to those files should be removed from their
respective csproj files.