You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Assaf Arkin (JIRA)" <ji...@apache.org> on 2008/07/08 01:14:31 UTC
[jira] Commented: (BUILDR-99) Tests should be run according to
dependency order
[ https://issues.apache.org/jira/browse/BUILDR-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611395#action_12611395 ]
Assaf Arkin commented on BUILDR-99:
-----------------------------------
Indeed. If we change this to use dependency, then moduleB would build first, test itself (package=>build=>test), so moduleA could then build and test itself.
> Tests should be run according to dependency order
> -------------------------------------------------
>
> Key: BUILDR-99
> URL: https://issues.apache.org/jira/browse/BUILDR-99
> Project: Buildr
> Issue Type: Improvement
> Components: Test frameworks
> Affects Versions: 1.3.1, 1.3.2
> Reporter: Lacton
> Priority: Minor
> Fix For: 1.3.3
>
>
> Let's have two modules, moduleA and moduleB.
> Let's say moduleA depends on moduleB.
> buildr compiles moduleB before compiling moduleA. This is the expected behavior.
> Then buildr runs tests from moduleA before running tests from moduleB. This behavior can be misleading. A defect in moduleB could make a test in moduleA fail. The test process will stop at moduleA and will not show the failing test in moduleB.
> Although the information that a test in moduleB is failing can be obtained by calling buildr with the 'test=all' option, it requires more intellectual effort to analyze the situation.
> I propose buildr runs tests according to the test dependency tree.
> define "test_order" do
> define "moduleA" do
> compile.with project('moduleB')
> package :jar
> end
> define "moduleB" do
> package :jar
> end
> end
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.