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 12:55:27 GMT

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

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

Try a project structure like:

Root
   rakeFile
   Project1
       Unit Tests
   Project2
       Unit Tests
   Project3
        Unit tests

If unit tests fail in Project1, Project2 and Project3 do not get run....which is not necessarily
what I would expect to see happen.   In an Ant based build system's all unit subsequent unit
tests will run, unless you tell it to fail when a test fails.

I believe we have test=all set up on the build machine, which correctly has it run all the
tests within a project (even if one fails), but it stops at the end of the project, and doesn't
build the rest in the chain.


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


Mime
View raw message