You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Antoine Toulme (JIRA)" <ji...@apache.org> on 2010/04/03 23:17:27 UTC

[jira] Commented: (BUILDR-413) Not All Tests are run if starting at top project level

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

Antoine Toulme commented on BUILDR-413:
---------------------------------------

I cannot reproduce the problem with a unit test.

I committed the couple of tests I attempted:
14:13:45~/w/buildr>svn ci spec/core/test_spec.rb -m "more specs to try to reproduce BUILDR-413, no luck so far"
Sending        spec/core/test_spec.rb
Transmitting file data .
Committed revision 930582.

I'm not sure what happens. Are you sure it stops executing tests ? either in the project or in other projects ?

> 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: 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.