I changed Assertion.AssertEquals to Assert.AreEqual but it had no effect. I
also ran the test from the console, avoiding NMaven entirely and the tests
don't run.
Even though two classes may have the same package name and class, if they
are loaded from separate assemblies, then the CLR loads them into different
application domains and treats them as different classes. I think that what
it happening is that the unit-console is loading up its version of
NUnit.Framework (without version in filename). Nunit-console is then only
looking for attributes/annotation from its version of
NUnit.Frameworkassembly. The NUnit test class attributes that we have
created are loaded
from NUnit.Framework with the version in the assembly filename. So the
annotations/attributes never match when nunit-console looks for them.
Good catch! I'll keep digging.
Shane
On Jan 23, 2008 9:02 AM, Shane Isbell <[EMAIL PROTECTED]> wrote:
> I'm seeing the same thing on Microsoft Windows. The
> MavenITmng0019BuildFailureOnNUnitFailure test doesn't fail on anything. Also
> I'm wondering why the NUnit test itself has:
> [Test]
> public void testSimple2() {
> // Forced failure
> Assertion.AssertEquals(2, 3);
> }
>
> but the TestResults.xml don't show the failure even from NUnit itself.
>
> I'll dig into this some more but when Evan comes back online, he should be
> able to jump in.
>
> Shane
>
> On Jan 22, 2008 11:51 PM, Erik Ramfelt <[EMAIL PROTECTED]> wrote:
>
> > Hi again
> >
> > Thanks for bearing with me, right now it feels like Im a little thick
> > as I cant get the tests to run as I expect.
> >
> > I looked into the "MavenITmng-0019-BuildFailureOnNUnitFailure" test,
> > which seems to have two unit tests and one of them should fail. But
> > when i look in the log.txt from that integration test run, the build
> > is successful. The reason why the build is successful might be that no
> > tests have been executed.
> >
> > I also saw that the java integration test implementation does not do
> > any assertion on the build result (executing "test"), and that might
> > be why the integration test is reported as passed.
> >
> > Isnt the unit tests supposed to be executed in the 0019 test?
> >
> >
> > Here is the log.txt for the 0019 test
> > (/tmp/MavenITmng-0019-BuildFailureOnNUnitFailure/log.txt):
> > -------------------------------------------------
> > [INFO] Scanning for projects...
> > [INFO] Searching repository for plugin with prefix: 'clean'.
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Building NMaven.It.It00019
> > [INFO] task-segment: [clean:clean, test]
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] [clean:clean]
> > [INFO] Deleting directory
> > /tmp/MavenITmng-0019-BuildFailureOnNUnitFailure/target
> > [INFO] Deleting directory
> > /tmp/MavenITmng-0019-BuildFailureOnNUnitFailure/target/classes
> > [INFO] Deleting directory
> > /tmp/MavenITmng-0019-BuildFailureOnNUnitFailure/target/test-classes
> > [INFO] Deleting directory
> > /tmp/MavenITmng-0019-BuildFailureOnNUnitFailure/target/site
> > [INFO] [compiler:generate-assembly-info]
> > [INFO] NMAVEN-902-000: Generating Assembly Info: Language = C_SHARP
> > [INFO] [compiler:process-sources]
> > [INFO] NMAVEN-904-001: No source files to copy
> > [INFO] [compiler:compile]
> > [INFO] .NET Vendor: NOVELL
> > NMAVEN-040-003: Error Log not set: Will use java.util.logging.Logger
> > NMAVEN-040-000: Executed command: Commandline = /bin/sh -c "gmcs
> > /out:/tmp/MavenITmng-0019-BuildFailureOnNUnitFailure/target/NMaven.It.It0019-
> > 1.0.0.dll
> > /target:library
> >
> > /recurse:/tmp/MavenITmng-0019-BuildFailureOnNUnitFailure/target/build-sources/**
> > /warnaserror- /reference:System.Drawing
> > /reference:System.Windows.Forms /reference:System.Web.Services
> >
> > /doc:/tmp/MavenITmng-0019-BuildFailureOnNUnitFailure/target/comments.xml",
> > Result = 0
> > [INFO] [compiler:process-test-sources]
> > [INFO] NMAVEN-904-002: Copying source files: From =
> > /tmp/MavenITmng-0019-BuildFailureOnNUnitFailure/test, To =
> >
> > /tmp/MavenITmng-0019-BuildFailureOnNUnitFailure/target/test-build-sources/test-sources,
> > File Count = 1
> > [INFO] [compiler:test-compile]
> > [INFO] .NET Vendor: NOVELL
> > NMAVEN-040-003: Error Log not set: Will use java.util.logging.Logger
> > 2008-jan-22 22:25:59
> >
> > org.apache.maven.dotnet.compiler.CommandExecutor$Factory$1$ErrorStreamConsumer
> > consumeLine
> > VARNING:
> > /tmp/MavenITmng-0019-BuildFailureOnNUnitFailure/target/test-build-sources/test-sources/It0007.cs(10,17):
> >
> > warning CS0618: `NUnit.Framework.Assertion' is obsolete: `Use Assert
> > class instead'
> > 2008-jan-22 22:25:59
> >
> > org.apache.maven.dotnet.compiler.CommandExecutor$Factory$1$ErrorStreamConsumer
> > consumeLine
> > VARNING:
> > /tmp/MavenITmng-0019-BuildFailureOnNUnitFailure/target/test-build-sources/test-sources/It0007.cs(16,17):
> > warning CS0618: `NUnit.Framework.Assertion' is obsolete: `Use Assert
> > class instead'
> > Compilation succeeded - 2 warning(s)
> > NMAVEN-040-000: Executed command: Commandline = /bin/sh -c "gmcs
> >
> > /out:/tmp/MavenITmng-0019-BuildFailureOnNUnitFailure/target/NMaven.It.It0019-
> > 1.0.0-test.dll
> > /target:library
> > /recurse:/tmp/MavenITmng-0019-BuildFailureOnNUnitFailure/target/test-build-sources/**
> >
> >
> > /reference:/home/hudson/.m2/repository/org/apache/maven/dotnet/NUnit.Framework/2.4.6-incubating-SNAPSHOT/NUnit.Framework-
> > 2.4.6-incubating-SNAPSHOT.dll
> > /reference:/tmp/MavenITmng-0019-BuildFailureOnNUnitFailure/target/NMaven.It.It0019-
> > 1.0.0.dll
> > /warnaserror- /reference:System.Drawing
> > /reference:System.Windows.Forms /reference:System.Web.Services",
> > Result = 0
> > [INFO] [dotnet-test:test]
> > [INFO]
> > [INFO] Tests run: 0, Failures: 0, Not run: 0, Time: 0.069 seconds
> > [INFO]
> > [INFO]
> > [INFO] Done executing tests..
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] BUILD SUCCESSFUL
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Total time: 28 seconds
> > [INFO] Finished at: Tue Jan 22 22:26:07 CET 2008
> > [INFO] Final Memory: 5M/11M
> > [INFO]
> > ------------------------------------------------------------------------
> >
> >
> > On Jan 17, 2008 10:31 PM, Shane Isbell <[EMAIL PROTECTED]> wrote:
> > > If you run mvn install -P run-its, it will run 18 or so IT tests.
> > NUnit is
> > > now in the snapsho repo so you don't need to install with the script.
> > >
> > > <dependencies>
> > > <dependency>
> > > <groupId>org.apache.maven.dotnet</groupId>
> > > <artifactId>NUnit.Framework</artifactId>
> > > <version>2.4.6-incubating-SNAPSHOT </version>
> > > <type>dotnet:library</type>
> > > <scope>test</scope>
> > > </dependency>
> > > </dependencies>
> > >
> > > <repositories>
> > > <repository>
> > > <id>m2-snapshot</id>
> > > <name>Maven2 Snapshot Repository</name>
> > > <url> http://people.apache.org/repo/m2-snapshot-repository/
> > </url>
> > > <snapshots>
> > > <enabled>true</enabled>
> > > </snapshots>
> > > </repository>
> > > </repositories>
> > >
> > > Shane
> > >
> > >
> > >
> > > On Jan 17, 2008 1:09 PM, Erik Ramfelt < [EMAIL PROTECTED]> wrote:
> > >
> > > > Im running debian/linux and mono so I could give it a try. Could
> > > > anyone share an nmaven example project that works with trunk so I
> > dont
> > > > have to fight a faulty project setup?
> > > >
> > > > This is what Ive done with trunk:
> > > > * mvn install
> > > > * mvn install:install-file
> > > > -Dfile=./thirdparty/NUnit/NUnit.Framework-2.4.6-incubating.dll
> > > > -DpomFile=./thirdparty/NUnit/NUnit.Framework- 2.4.6-incubating.pom
> > > > -DgroupId=org.apache.maven.dotnet -DartifactId=NUnit.Framework
> > > > -Dversion=2.4.6-incubating
> > > >
> > > > Is there anything else I have to do?
> > > >
> > > > Regards
> > > > //Erik
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Jan 17, 2008 9:23 PM, Shane Isbell <[EMAIL PROTECTED]>
> > wrote:
> > > > > We really need to get people pounding on NMaven, particularly with
> > Mono
> > > and
> > > > > Linux. We've got everything in that we intend to release for 0.15,
> > so
> > > now it
> > > > > is a matter of getting some testing done on the trunk. Then we
> > should be
> > > > > ready to package and call a vote on our first release.
> > > > >
> > > > > Thanks,
> > > > > Shane
> > > > >
> > > >
> > >
> > >
> >
>
>
