Mailing-List: contact commits-help@buildr.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@buildr.apache.org
Date: Wed, 22 Jun 2011 10:11:27 +0000 (UTC)
From: "Peter Donald (JIRA)" <jira@apache.org>
To: buildr-commits@incubator.apache.org
Message-ID: 
 <107397052.28725.1308737487109.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (BUILDR-301) TestNG doesn't report failure if more
 than one test fails
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/BUILDR-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Donald closed BUILDR-301.
-------------------------------


> TestNG doesn't report failure if more than one test fails
> ---------------------------------------------------------
>
>                 Key: BUILDR-301
>                 URL: https://issues.apache.org/jira/browse/BUILDR-301
>             Project: Buildr
>          Issue Type: Bug
>          Components: Test frameworks
>    Affects Versions: 1.3.4
>         Environment: Tested on Linux (Fedora, Debian/Ubuntu)
>            Reporter: Martin Grotzke
>            Assignee: Alex Boisvert
>             Fix For: 1.3.5
>
>
> This issue is related to the report on the mailing list:
> http://n2.nabble.com/Build-completes-successfully-on-configuration-failures-and-skipped-tests-td3332816.html#a3332816
> I reproduced what we encountered in a simple project that has these test classes
> - a BaseTest with a beforMethod that fails and a test method (that is skipped)
> - a Test1 that extends BaseTest, with a test method that is also skipped.
> This is the output of a `buildr clean test':
> [grotzke@mescalin testmodule]$ buildr clean test
> (in /home/grotzke/proj/buildr-sandbox, development)
> Cleaning buildr-sandbox:testmodule
> Testing buildr-sandbox:testmodule
> Compiling buildr-sandbox:testmodule into /home/grotzke/proj/buildr-sandbox/testmodule/target/classes
> Compiling buildr-sandbox:testmodule:test into /home/grotzke/proj/buildr-sandbox/testmodule/target/test/classes
> Running tests in buildr-sandbox:testmodule
> Running TestNG in buildr-sandbox:testmodule
> [Parser] Running:
>   buildr-sandbox-testmodule
> FAILED CONFIGURATION: @BeforeMethod beforeBaseTestMethod
> java.lang.RuntimeException: s.th. failed here...
>         at de.javakaffee.buildr.sandbox.testmodule.BaseTest.beforeBaseTestMethod(BaseTest.scala:10)
> ... Removed 24 stack frames
> SKIPPED CONFIGURATION: @BeforeMethod beforeBaseTestMethod
> SKIPPED CONFIGURATION: @BeforeMethod beforeBaseTestMethod
> SKIPPED: testBase
> SKIPPED: testClass1
> SKIPPED: testBase
> ===============================================
>     Command line test
>     Tests run: 3, Failures: 0, Skips: 3
>     Configuration Failures: 1, Skips: 2
> ===============================================
> ===============================================
> buildr-sandbox-testmodule
> Total tests run: 3, Failures: 0, Skips: 3
> Configuration Failures: 1, Skips: 2
> ===============================================
> Completed in 4.305s
> The project can be found here:
> http://github.com/magro/buildr-sandbox/tree/master

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira