buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "lacton (JIRA)" <j...@apache.org>
Subject [jira] Created: (BUILDR-139) Incremental test run
Date Tue, 26 Aug 2008 22:02:44 GMT
Incremental test run
--------------------

                 Key: BUILDR-139
                 URL: https://issues.apache.org/jira/browse/BUILDR-139
             Project: Buildr
          Issue Type: Improvement
          Components: Core features
    Affects Versions: 1.3.2
            Reporter: lacton
             Fix For: 1.3.3


Tests should be run in an incremental way, just like compile or package.  If nothing has changed,
the default behavior should be to skip the tests.  If anything has changed, it should be to
run the tests.  This decision should be on a per-project basis.

A test run is needed if and only if
1. there one or more test dependencies with a timestamp later than the time of the last successful
test run for this project
OR
2. there is no record of a successful test run for this project

User choices should override all incremental mechanisms. For instance, the following should
have precedence.
- test=all or test=no (or their equivalent with environment variables)
- test:SomeTest

In this context, a change means anything that could affect the project, be it a change in
a source file, in a resource, in a required project, in the buildfile or in build.yml.

Individual project test and build tasks should run the tests or not, based on the above criteria.

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