maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Rosenvold (JIRA)" <>
Subject [jira] Updated: (SUREFIRE-645) Meaningful message when test has no runnable methods
Date Sun, 02 Jan 2011 19:21:58 GMT


Kristian Rosenvold updated SUREFIRE-645:

    Attachment: surefire645_revised.patch

Thanks for the patch, Stefan !

I must admit that there are *so* many corner cases and variations of this exact issue and
I would really like to be able to reproduce each variety before committing any fixes. I have
revised the patch slightly and added a template project for an integration test.

The problem is that the template project does not reproduce the behavior you are describing,
and I have been unable to make it do so. This is probably because your issue does not mention
versions/providers etc. Could you please tweak the files/project in surefire-integration-tests/src/test/resources/norunnableTests/
so  running a "mvn -Dsurefire.version=2.7.2-SNAPSHOT test" will reproduce the problem you
are fixing. Once you re-submit this change I will certainly apply the patch.


> Meaningful message when test has no runnable methods
> ----------------------------------------------------
>                 Key: SUREFIRE-645
>                 URL:
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: Maven Surefire Plugin
>    Affects Versions: Backlog
>            Reporter: Stefan Birkner
>             Fix For: 2.7.2
>         Attachments: extendedErrorMessage.patch, surefire645_revised.patch
> If there's a test class without any runnable methods, the test fails with an error. The
output to the command line is:
> Tests in error: 
>   initializationError(EmptyTest)
> The supplied patch extends this message for all errors. For the error at hand, the output
to the command line will be:
> Tests in error: 
>   initializationError(EmptyTest): No runnable methods

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message