You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Rafal Rusin (JIRA)" <ji...@apache.org> on 2010/05/07 20:33:47 UTC
[jira] Created: (BUILDR-431) 'buildr test' runs tests from all
dependent modules while invoked from a particular module
'buildr test' runs tests from all dependent modules while invoked from a particular module
------------------------------------------------------------------------------------------
Key: BUILDR-431
URL: https://issues.apache.org/jira/browse/BUILDR-431
Project: Buildr
Issue Type: Bug
Affects Versions: 1.3.5
Reporter: Rafal Rusin
To reproduce it, please use APACHE_ODE_1.X and enter bpel-compiler. Then run
buildr _1.3.5_ test
ode-utils tests are shown to be executed (while they shouldn't):
buildr _1.3.5_ test
(in /home/joker/ode-1.X, development)
Testing ode:bpel-compiler
Running tests in ode:utils
Trying to override old definition of datatype junit
[junit] Testsuite: org.apache.ode.utils.DOMUtilsTest
[junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 1,498 sec
[junit]
[junit] Testcase: testParseInputStream took 0,534 sec
[junit] Testcase: testParseInputSource took 0,005 sec
[junit] Testcase: testNewDocument took 0 sec
[junit] Testcase: testSerializeDom took 0,034 sec
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (BUILDR-431) 'buildr test' runs tests from all
dependent modules while invoked from a particular module
Posted by Alex Boisvert <al...@gmail.com>.
I (still) can't comment on bugs in Jira so I'll comment here.
I believe I've answered this question/issue before:
http://www.mail-archive.com/users@buildr.apache.org/msg01295.html
alex
On Fri, May 7, 2010 at 11:33 AM, Rafal Rusin (JIRA) <ji...@apache.org> wrote:
> 'buildr test' runs tests from all dependent modules while invoked from a
> particular module
>
> ------------------------------------------------------------------------------------------
>
> Key: BUILDR-431
> URL: https://issues.apache.org/jira/browse/BUILDR-431
> Project: Buildr
> Issue Type: Bug
> Affects Versions: 1.3.5
> Reporter: Rafal Rusin
>
>
> To reproduce it, please use APACHE_ODE_1.X and enter bpel-compiler. Then
> run
> buildr _1.3.5_ test
>
> ode-utils tests are shown to be executed (while they shouldn't):
>
> buildr _1.3.5_ test
> (in /home/joker/ode-1.X, development)
> Testing ode:bpel-compiler
> Running tests in ode:utils
> Trying to override old definition of datatype junit
> [junit] Testsuite: org.apache.ode.utils.DOMUtilsTest
> [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 1,498 sec
> [junit]
> [junit] Testcase: testParseInputStream took 0,534 sec
> [junit] Testcase: testParseInputSource took 0,005 sec
> [junit] Testcase: testNewDocument took 0 sec
> [junit] Testcase: testSerializeDom took 0,034 sec
>
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
[jira] Commented: (BUILDR-431) 'buildr test' runs tests from all
dependent modules while invoked from a particular module
Posted by "lacton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865434#action_12865434 ]
lacton commented on BUILDR-431:
-------------------------------
Antoine,
Printing "test=only is not specified, we will test the dependent projects" would not be 100% accurate, because dependent projects will be tested *only* if something changed in them, or in one of their transitively dependent projects.
A clearer version could be:
$ buildr bar:test
(in /path, development)
Testing project foo because it has untested changes. Use 'test=only' if you want to prevent this behavior.
...
Maybe this should be printed only if a verbose or trace option was activated. Otherwise, I'm afraid buildr will lose its Unix-like terseness.
> 'buildr test' runs tests from all dependent modules while invoked from a particular module
> ------------------------------------------------------------------------------------------
>
> Key: BUILDR-431
> URL: https://issues.apache.org/jira/browse/BUILDR-431
> Project: Buildr
> Issue Type: Bug
> Affects Versions: 1.3.5
> Reporter: Rafal Rusin
> Assignee: Antoine Toulme
>
> To reproduce it, please use APACHE_ODE_1.X and enter bpel-compiler. Then run
> buildr _1.3.5_ test
> ode-utils tests are shown to be executed (while they shouldn't):
> buildr _1.3.5_ test
> (in /home/joker/ode-1.X, development)
> Testing ode:bpel-compiler
> Running tests in ode:utils
> Trying to override old definition of datatype junit
> [junit] Testsuite: org.apache.ode.utils.DOMUtilsTest
> [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 1,498 sec
> [junit]
> [junit] Testcase: testParseInputStream took 0,534 sec
> [junit] Testcase: testParseInputSource took 0,005 sec
> [junit] Testcase: testNewDocument took 0 sec
> [junit] Testcase: testSerializeDom took 0,034 sec
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-431) 'buildr test' runs tests from all
dependent modules while invoked from a particular module
Posted by "lacton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865299#action_12865299 ]
lacton commented on BUILDR-431:
-------------------------------
"One last note on running tests. By default when you run tests, Buildr will automatically run all transitive test dependencies. This mean if you run "buildr test" inside project bar and bar depends on project foo, Buildr will first run tests in project foo if there have been any changes affecting foo that haven't been taken into account yet. This behavior often surprises people, especially when they are trying to get things done and only care about tests in bar at that moment. For those times when you'd like to focus your testing on specific projects, Buildr has the only option that will only run tests for projects specified on the command line,
$ buildr test=only bar:test"
from http://buildr.apache.org/testing.html
So, it's not a regression, it's an evolution.
> 'buildr test' runs tests from all dependent modules while invoked from a particular module
> ------------------------------------------------------------------------------------------
>
> Key: BUILDR-431
> URL: https://issues.apache.org/jira/browse/BUILDR-431
> Project: Buildr
> Issue Type: Bug
> Affects Versions: 1.3.5
> Reporter: Rafal Rusin
> Assignee: Antoine Toulme
>
> To reproduce it, please use APACHE_ODE_1.X and enter bpel-compiler. Then run
> buildr _1.3.5_ test
> ode-utils tests are shown to be executed (while they shouldn't):
> buildr _1.3.5_ test
> (in /home/joker/ode-1.X, development)
> Testing ode:bpel-compiler
> Running tests in ode:utils
> Trying to override old definition of datatype junit
> [junit] Testsuite: org.apache.ode.utils.DOMUtilsTest
> [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 1,498 sec
> [junit]
> [junit] Testcase: testParseInputStream took 0,534 sec
> [junit] Testcase: testParseInputSource took 0,005 sec
> [junit] Testcase: testNewDocument took 0 sec
> [junit] Testcase: testSerializeDom took 0,034 sec
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (BUILDR-431) 'buildr test' runs tests from all
dependent modules while invoked from a particular module
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Toulme reassigned BUILDR-431:
-------------------------------------
Assignee: Antoine Toulme
> 'buildr test' runs tests from all dependent modules while invoked from a particular module
> ------------------------------------------------------------------------------------------
>
> Key: BUILDR-431
> URL: https://issues.apache.org/jira/browse/BUILDR-431
> Project: Buildr
> Issue Type: Bug
> Affects Versions: 1.3.5
> Reporter: Rafal Rusin
> Assignee: Antoine Toulme
>
> To reproduce it, please use APACHE_ODE_1.X and enter bpel-compiler. Then run
> buildr _1.3.5_ test
> ode-utils tests are shown to be executed (while they shouldn't):
> buildr _1.3.5_ test
> (in /home/joker/ode-1.X, development)
> Testing ode:bpel-compiler
> Running tests in ode:utils
> Trying to override old definition of datatype junit
> [junit] Testsuite: org.apache.ode.utils.DOMUtilsTest
> [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 1,498 sec
> [junit]
> [junit] Testcase: testParseInputStream took 0,534 sec
> [junit] Testcase: testParseInputSource took 0,005 sec
> [junit] Testcase: testNewDocument took 0 sec
> [junit] Testcase: testSerializeDom took 0,034 sec
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-431) 'buildr test' runs tests from all
dependent modules while invoked from a particular module
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865480#action_12865480 ]
Antoine Toulme commented on BUILDR-431:
---------------------------------------
Well, looks like the option doesn't do its job anyway, looking at Rafal's last comment. I'll work on a spec.
> 'buildr test' runs tests from all dependent modules while invoked from a particular module
> ------------------------------------------------------------------------------------------
>
> Key: BUILDR-431
> URL: https://issues.apache.org/jira/browse/BUILDR-431
> Project: Buildr
> Issue Type: Bug
> Affects Versions: 1.3.5
> Reporter: Rafal Rusin
> Assignee: Antoine Toulme
>
> To reproduce it, please use APACHE_ODE_1.X and enter bpel-compiler. Then run
> buildr _1.3.5_ test
> ode-utils tests are shown to be executed (while they shouldn't):
> buildr _1.3.5_ test
> (in /home/joker/ode-1.X, development)
> Testing ode:bpel-compiler
> Running tests in ode:utils
> Trying to override old definition of datatype junit
> [junit] Testsuite: org.apache.ode.utils.DOMUtilsTest
> [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 1,498 sec
> [junit]
> [junit] Testcase: testParseInputStream took 0,534 sec
> [junit] Testcase: testParseInputSource took 0,005 sec
> [junit] Testcase: testNewDocument took 0 sec
> [junit] Testcase: testSerializeDom took 0,034 sec
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-431) 'buildr test' runs tests from all
dependent modules while invoked from a particular module
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865330#action_12865330 ]
Antoine Toulme commented on BUILDR-431:
---------------------------------------
I think what we should do is print in the console that we are going to execute the tests from the dependent projects and why.
This way people get a grasp of that evolution real quick.
Something like:
test=only is not specified, we will test the dependent projects.
> 'buildr test' runs tests from all dependent modules while invoked from a particular module
> ------------------------------------------------------------------------------------------
>
> Key: BUILDR-431
> URL: https://issues.apache.org/jira/browse/BUILDR-431
> Project: Buildr
> Issue Type: Bug
> Affects Versions: 1.3.5
> Reporter: Rafal Rusin
> Assignee: Antoine Toulme
>
> To reproduce it, please use APACHE_ODE_1.X and enter bpel-compiler. Then run
> buildr _1.3.5_ test
> ode-utils tests are shown to be executed (while they shouldn't):
> buildr _1.3.5_ test
> (in /home/joker/ode-1.X, development)
> Testing ode:bpel-compiler
> Running tests in ode:utils
> Trying to override old definition of datatype junit
> [junit] Testsuite: org.apache.ode.utils.DOMUtilsTest
> [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 1,498 sec
> [junit]
> [junit] Testcase: testParseInputStream took 0,534 sec
> [junit] Testcase: testParseInputSource took 0,005 sec
> [junit] Testcase: testNewDocument took 0 sec
> [junit] Testcase: testSerializeDom took 0,034 sec
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-431) 'buildr test' runs tests from all
dependent modules while invoked from a particular module
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865260#action_12865260 ]
Rafal Rusin commented on BUILDR-431:
------------------------------------
Please note this is regression from _1.2.10_
> 'buildr test' runs tests from all dependent modules while invoked from a particular module
> ------------------------------------------------------------------------------------------
>
> Key: BUILDR-431
> URL: https://issues.apache.org/jira/browse/BUILDR-431
> Project: Buildr
> Issue Type: Bug
> Affects Versions: 1.3.5
> Reporter: Rafal Rusin
>
> To reproduce it, please use APACHE_ODE_1.X and enter bpel-compiler. Then run
> buildr _1.3.5_ test
> ode-utils tests are shown to be executed (while they shouldn't):
> buildr _1.3.5_ test
> (in /home/joker/ode-1.X, development)
> Testing ode:bpel-compiler
> Running tests in ode:utils
> Trying to override old definition of datatype junit
> [junit] Testsuite: org.apache.ode.utils.DOMUtilsTest
> [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 1,498 sec
> [junit]
> [junit] Testcase: testParseInputStream took 0,534 sec
> [junit] Testcase: testParseInputSource took 0,005 sec
> [junit] Testcase: testNewDocument took 0 sec
> [junit] Testcase: testSerializeDom took 0,034 sec
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-431) 'buildr test' runs tests from all
dependent modules while invoked from a particular module
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865421#action_12865421 ]
Rafal Rusin commented on BUILDR-431:
------------------------------------
OK, I tried that with no success. Any ideas why?
joker@joker-laptop:~/ode-1.X/bpel-compiler$ buildr _1.3.5_ test=only ode:bpel-test:test
(in /home/joker/ode-1.X, development)
Expecting the environment variable test to be 'no' or 'all', not sure what to do with only, so I'm just going to run all the tests and stop at failure.
Running tests in ode:utils
Trying to override old definition of datatype junit
[junit] Testsuite: org.apache.ode.utils.DOMUtilsTest
[junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 1,456 sec
[junit]
[junit] Testcase: testParseInputStream took 0,369 sec
[junit] Testcase: testParseInputSource took 0,006 sec
[junit] Testcase: testNewDocument took 0 sec
[junit] Testcase: testSerializeDom took 0,032 sec
[junit] Testcase: testConcurrentParse took 0,644 sec
[junit] Testcase: testIsEmptyElement took 0,004 sec
[junit] Testcase: testCloneNode took 0,003 sec
> 'buildr test' runs tests from all dependent modules while invoked from a particular module
> ------------------------------------------------------------------------------------------
>
> Key: BUILDR-431
> URL: https://issues.apache.org/jira/browse/BUILDR-431
> Project: Buildr
> Issue Type: Bug
> Affects Versions: 1.3.5
> Reporter: Rafal Rusin
> Assignee: Antoine Toulme
>
> To reproduce it, please use APACHE_ODE_1.X and enter bpel-compiler. Then run
> buildr _1.3.5_ test
> ode-utils tests are shown to be executed (while they shouldn't):
> buildr _1.3.5_ test
> (in /home/joker/ode-1.X, development)
> Testing ode:bpel-compiler
> Running tests in ode:utils
> Trying to override old definition of datatype junit
> [junit] Testsuite: org.apache.ode.utils.DOMUtilsTest
> [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 1,498 sec
> [junit]
> [junit] Testcase: testParseInputStream took 0,534 sec
> [junit] Testcase: testParseInputSource took 0,005 sec
> [junit] Testcase: testNewDocument took 0 sec
> [junit] Testcase: testSerializeDom took 0,034 sec
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.