activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-5552) introduce a smoke-test profile that is enabled by default and during release:prepare
Date Fri, 30 Jan 2015 11:58:34 GMT

     [ https://issues.apache.org/jira/browse/AMQ-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gary Tully updated AMQ-5552:
----------------------------
    Description: 
Users should be able to do $>mvn install on trunk or the source distribution and get a
validated (smoke-tested) distribution in < 10  minutes.
The smoke-test profile should be enabled for release:prepare

At the moment, more than 3k tests are run, they are not reliable enough and the build is gone
for a number of hours. This gives a bad first impression.
Or course we should continue to improve the test suite but this has a totally different focus.

The smoke-test profile takes a smart cross section of tests in each module that validate core
functionality. 

It will be an interesting challenge to get the selection right; balancing typical use cases
with coverage with speed etc.

The tests should be:
 * representative of the module functionality
 * clean - no hard-coded ports and use only space on target
 * fast
 * reliable
 * can be run in parallel (maybe if it allows more tests to be run in the same time frame)
 

  was:
Users should be able to do $>mvn install on trunk or the source distribution and get a
validated (smoke-tested) distribution in < 10  minutes.
The smoke-test profile should be enabled for release:prepare

At the moment, more than 3k tests are run, they are not reliable enough and the build is gone
for a number of hours. This gives a bad first impression.
Or course we should continue to improve the test suite but this has a totally different focus.

The smoke-test profile takes a smart cross section of tests in each module that validate core
functionality. 

It will be an interesting challenge to get the selection right; balancing typical use cases
with coverage with speed etc.

But the tests should be:
 * clean - no hard-coded ports and use only space on target
 * fast
 * reliable
 * can be run in parallel (maybe if it allows more tests to be run in the same time frame)
 


> introduce a smoke-test profile that is enabled by default and during release:prepare
> ------------------------------------------------------------------------------------
>
>                 Key: AMQ-5552
>                 URL: https://issues.apache.org/jira/browse/AMQ-5552
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Distribution, Test Cases
>    Affects Versions: 5.11.0
>            Reporter: Gary Tully
>              Labels: distribution, mvn, smoke, tests, validation
>             Fix For: 5.12.0
>
>
> Users should be able to do $>mvn install on trunk or the source distribution and get
a validated (smoke-tested) distribution in < 10  minutes.
> The smoke-test profile should be enabled for release:prepare
> At the moment, more than 3k tests are run, they are not reliable enough and the build
is gone for a number of hours. This gives a bad first impression.
> Or course we should continue to improve the test suite but this has a totally different
focus.
> The smoke-test profile takes a smart cross section of tests in each module that validate
core functionality. 
> It will be an interesting challenge to get the selection right; balancing typical use
cases with coverage with speed etc.
> The tests should be:
>  * representative of the module functionality
>  * clean - no hard-coded ports and use only space on target
>  * fast
>  * reliable
>  * can be run in parallel (maybe if it allows more tests to be run in the same time frame)
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message