[JBoss JIRA] (WFLY-612) TS: Print help banner on `mvn install` without params.
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-612?page=com.atlassian.jira.plugin.s... ]
Jason Greene moved AS7-2451 to WFLY-612:
----------------------------------------
Project: WildFly (was: Application Server 7)
Key: WFLY-612 (was: AS7-2451)
Component/s: (was: Test Suite)
Fix Version/s: (was: 7.1.1.Final)
> TS: Print help banner on `mvn install` without params.
> ------------------------------------------------------
>
> Key: WFLY-612
> URL: https://issues.jboss.org/browse/WFLY-612
> Project: WildFly
> Issue Type: Sub-task
> Reporter: Ondrej Zizka
> Assignee: Ondrej Zizka
>
> Jaikiran:
> {qoute}
> Would it be possible to somehow print out all the available options and
> params that need to used, when you run mvn clean install from the
> testsuite modules? Something like a help?
> {qoute}
> Not sure if it will be possible to check the condition "There are no params", but we can print it every time as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (WFLY-607) TS: Define testsuite acceptance test (a testsuite for the testsuite)
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-607?page=com.atlassian.jira.plugin.s... ]
Jason Greene moved AS7-2270 to WFLY-607:
----------------------------------------
Project: WildFly (was: Application Server 7)
Key: WFLY-607 (was: AS7-2270)
Component/s: (was: Test Suite)
Fix Version/s: (was: 7.1.1.Final)
> TS: Define testsuite acceptance test (a testsuite for the testsuite)
> --------------------------------------------------------------------
>
> Key: WFLY-607
> URL: https://issues.jboss.org/browse/WFLY-607
> Project: WildFly
> Issue Type: Sub-task
> Reporter: Ondrej Zizka
> Assignee: Ondrej Zizka
>
> Define a procedure to perform before committing something to the testsuite.
> Create scripts to help determining whether given testsuite is okay to be committed.
> E.g.
> {code}
> IN='-DallTests -Dinteg-tests -Dcluster-tests -Dbasic-tests -Dbenchmark-tests -Dsmoke-tests -Dstress-tests -Ddomain-tests -Dcompat-tests';
> for GROUP in $(echo $IN | tr ";" "\n"); do
> ## Create results dir.
> RES_DIR=~/work/AS7/res/$GROUP
> mkdir -p $RES_DIR
> ## Run the testsuite.
> ./integration-tests.sh clean -DallTests;
> ./integration-tests.sh install $GROUP;
> ## Archive the reports.
> for REPORT in `find testsuite -name 'TEST-*.xml' -or -name '*TestCase.txt' -or -name '*TestCase-output.txt'`; do
> SUB_DIR=`dirname $REPORT | sed 's#testsuite/##' | sed 's#/target/surefire-reports##'`
> mkdir -p $RES_DIR/$SUB_DIR
> cp $REPORT $RES_DIR/$SUB_DIR
> done
> ## Run the testsuite for 2nd time to ensure that unclean run works too.
> ./integration-tests.sh install $GROUP;
> done
> ## Create a JUnitDiff report.
> {code}
> Also, check what's being passed to `mvn` on various params combinations:
> {code}
> ./build.sh -DallTests
> ./build.sh -DallTests -Dfoo
> ./build.sh install -DallTests
> ./build.sh clean -DallTests
> ./build.sh clean install -DallTests -Dfoo
> ./integration-tests.sh -DallTests;
> ./integration-tests.sh install -DallTests;
> ./integration-tests.sh clean -DallTests;
> ./integration-tests.sh clean install -DallTests -Dfoo;
> ./integration-tests.sh test -DallTests -Dfoo;
> ...
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (WFLY-609) TS: Move smoke and integration tests before the domain stuff.
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-609?page=com.atlassian.jira.plugin.s... ]
Jason Greene moved AS7-2443 to WFLY-609:
----------------------------------------
Project: WildFly (was: Application Server 7)
Key: WFLY-609 (was: AS7-2443)
Component/s: (was: Test Suite)
Fix Version/s: (was: 7.1.0.CR1)
> TS: Move smoke and integration tests before the domain stuff.
> -------------------------------------------------------------
>
> Key: WFLY-609
> URL: https://issues.jboss.org/browse/WFLY-609
> Project: WildFly
> Issue Type: Sub-task
> Reporter: Ondrej Zizka
> Assignee: Ondrej Zizka
>
> {query}
> (21:31:55) bstansberry: OndrejZizka1: I'd like to re-order the testsuite execution a bit but am a bit lost on what's driving the current order
> (21:33:11) bstansberry: OndrejZizka1: it would be better if smoke and integration tests ran before the domain stuff, as the domain stuff is slow and just delays an overall failure if one of the more numerous smoke/integration tests fails
> {query}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months