buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Carver (JIRA)" <j...@apache.org>
Subject [jira] Commented: (BUILDR-413) Not All Tests are run if starting at top project level
Date Mon, 05 Apr 2010 17:31:27 GMT

    [ https://issues.apache.org/jira/browse/BUILDR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853448#action_12853448
] 

David Carver commented on BUILDR-413:
-------------------------------------

is test=all case sensitive?   In one of our jobs we have it as TEST=all



> Not All Tests are run if starting at top project level
> ------------------------------------------------------
>
>                 Key: BUILDR-413
>                 URL: https://issues.apache.org/jira/browse/BUILDR-413
>             Project: Buildr
>          Issue Type: Bug
>          Components: Test frameworks
>    Affects Versions: 1.3.5
>            Reporter: David Carver
>            Assignee: Antoine Toulme
>             Fix For: 1.4
>
>         Attachments: buildr-testall.zip, IrraticTestPattern.png
>
>
> When running unit tests, and running from the top level project using test=all does not
continue running all the tests.  It runs all the tests until there is a failure in a project,
and then runs the all the tests in that project, but then stops running tests.   Ideally,
it should continue running tests in all the other projects as well as there may be additional
tests that need to be reported as failures.   This is critical when doing a continuous integration
build so that the developers get proper feedback on the state of the build.
> I'll attach a screen shot from a Hudson build that shows the pattern I'm talking about.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message