You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "David Carver (JIRA)" <ji...@apache.org> on 2010/04/01 19:34:27 UTC
[jira] Created: (BUILDR-413) Not All Tests are run if starting at
top project level
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
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.
[jira] Updated: (BUILDR-413) Not All Tests are run if starting at
top project level
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Toulme updated BUILDR-413:
----------------------------------
Fix Version/s: 1.4.1
(was: 1.4)
Moving this to 1.4.1. We could not reproduce this - yet.
> 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.1
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (BUILDR-413) Not All Tests are run if starting at
top project level
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853370#action_12853370 ]
Alex Boisvert commented on BUILDR-413:
--------------------------------------
Yes, I saw that. Since I did try it manually (for integration testing's sake), I figured I might as well attach it.
> 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.
[jira] Commented: (BUILDR-413) Not All Tests are run if starting at
top project level
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (BUILDR-413) Not All Tests are run if starting at
top project level
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert updated BUILDR-413:
---------------------------------
Fix Version/s: Wish List
(was: 1.4.2)
Moving out of 1.4.2 since we can't reproduce.
> 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: Wish List
>
> 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.
[jira] Issue Comment Edited: (BUILDR-413) Not All Tests are run if
starting at top project level
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853365#action_12853365 ]
Alex Boisvert edited comment on BUILDR-413 at 4/5/10 2:02 PM:
--------------------------------------------------------------
I've created the same structure (see attachment buildr-testall.zip) and I cannot reproduce this,
.
|-- buildfile
|-- a
| `-- src
| |-- main
| | `-- java
| | `-- HelloA.java
| `-- test
| `-- java
| `-- HelloATest.java
|-- b
| `-- src
| |-- main
| | `-- java
| | `-- HelloB.java
| `-- test
| `-- java
| `-- HelloBTest.java
`-- c
`-- src
|-- main
| `-- java
| `-- HelloC.java
`-- test
`-- java
`-- HelloCTest.java
Tests in A are supposed to fail.
Running "buildr test" stops at project A, as expected.
Running "buildr test=all" reports error for project A and reports successes for projects B and C.
was (Author: boisvert):
I've created the same structure (see attachment buildr-testall.zip) and I cannot reproduce this,
.
|-- buildfile
|-- a
| `-- src
| |-- main
| | `-- java
| | `-- HelloA.java
| `-- test
| `-- java
| `-- HelloATest.java
|-- b
| `-- src
| |-- main
| | `-- java
| | `-- HelloB.java
| `-- test
| `-- java
| `-- HelloBTest.java
`-- c
`-- src
|-- main
| `-- java
| `-- HelloC.java
`-- test
`-- java
`-- HelloBTest.java
Tests in A are supposed to fail.
Running "buildr test" stops at project A, as expected.
Running "buildr test=all" reports error for project A and reports successes for projects B and C.
> 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.
[jira] Assigned: (BUILDR-413) Not All Tests are run if starting at
top project level
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Toulme reassigned BUILDR-413:
-------------------------------------
Assignee: Antoine Toulme
> 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.
[jira] Updated: (BUILDR-413) Not All Tests are run if starting at
top project level
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Toulme updated BUILDR-413:
----------------------------------
Fix Version/s: 1.4.2
(was: 1.4.1)
> 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.2
>
> 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.
[jira] Commented: (BUILDR-413) Not All Tests are run if starting at
top project level
Posted by "David Carver (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (BUILDR-413) Not All Tests are run if starting at
top project level
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853367#action_12853367 ]
Antoine Toulme commented on BUILDR-413:
---------------------------------------
That's what I did earlier in r930582.
> 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.
[jira] Updated: (BUILDR-413) Not All Tests are run if starting at
top project level
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Toulme updated BUILDR-413:
----------------------------------
Fix Version/s: 1.4
Targeting 1.4. Damn, Chuck is scary.
> 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.
[jira] Commented: (BUILDR-413) Not All Tests are run if starting at
top project level
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853372#action_12853372 ]
Alex Boisvert commented on BUILDR-413:
--------------------------------------
I also tried with Cobertura instrumetation just in case there was some kind of anomaly there, but everything works as expected.
> 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.
[jira] Updated: (BUILDR-413) Not All Tests are run if starting at
top project level
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert updated BUILDR-413:
---------------------------------
Attachment: buildr-testall.zip
> 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.
[jira] Commented: (BUILDR-413) Not All Tests are run if starting at
top project level
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853385#action_12853385 ]
Antoine Toulme commented on BUILDR-413:
---------------------------------------
Alex, the project in question is ODE branch 1.x. Not sure really what happens.
OK, maybe something else I can try: try using different test frameworks in subprojects.
> 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.
[jira] Commented: (BUILDR-413) Not All Tests are run if starting at
top project level
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853365#action_12853365 ]
Alex Boisvert commented on BUILDR-413:
--------------------------------------
I've created the same structure (see attachment buildr-testall.zip) and I cannot reproduce this,
.
|-- buildfile
|-- a
| `-- src
| |-- main
| | `-- java
| | `-- HelloA.java
| `-- test
| `-- java
| `-- HelloATest.java
|-- b
| `-- src
| |-- main
| | `-- java
| | `-- HelloB.java
| `-- test
| `-- java
| `-- HelloBTest.java
`-- c
`-- src
|-- main
| `-- java
| `-- HelloC.java
`-- test
`-- java
`-- HelloBTest.java
Tests in A are supposed to fail.
Running "buildr test" stops at project A, as expected.
Running "buildr test=all" reports error for project A and reports successes for projects B and C.
> 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.
[jira] Commented: (BUILDR-413) Not All Tests are run if starting at
top project level
Posted by "David Carver (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (BUILDR-413) Not All Tests are run if starting at
top project level
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853451#action_12853451 ]
Alex Boisvert commented on BUILDR-413:
--------------------------------------
No, not case-sensitive.
> 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.
[jira] Updated: (BUILDR-413) Not All Tests are run if starting at
top project level
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert updated BUILDR-413:
---------------------------------
Attachment: buildr-testall.zip
> 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.
[jira] Commented: (BUILDR-413) Not All Tests are run if starting at
top project level
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853305#action_12853305 ]
Alex Boisvert commented on BUILDR-413:
--------------------------------------
I can't reproduce this either; we'll need a better idea of your project's structure to investigate.
> 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.
[jira] Updated: (BUILDR-413) Not All Tests are run if starting at
top project level
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert updated BUILDR-413:
---------------------------------
Attachment: (was: buildr-testall.zip)
> 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.
[jira] Commented: (BUILDR-413) Not All Tests are run if starting at
top project level
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888081#action_12888081 ]
Antoine Toulme commented on BUILDR-413:
---------------------------------------
I am thinking it might be due to a deadlock that's occurring with the current ODE build. I am working on resolving it.
> 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: Wish List
>
> 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.
[jira] Updated: (BUILDR-413) Not All Tests are run if starting at
top project level
Posted by "David Carver (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Carver updated BUILDR-413:
--------------------------------
Attachment: IrraticTestPattern.png
Image that shows the irratic test pattern this causes. All the tests should run instead of stopping in the middle as soon as some fail.
> 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
> 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.