[jboss-as7-dev] Test Suite Changes

[Shelly McGowan]

>From August:

http://lists.jboss.org/pipermail/jboss-as7-dev/2011-August/003452.html

Shelly


----- Original Message -----
From: "Shelly McGowan" <smcgowan at redhat.com>
To: "Thomas Diesler" <thomas.diesler at jboss.com>
Cc: jboss-as7-dev at lists.jboss.org, "Darran Lofthouse" <darran.lofthouse at jboss.com>
Sent: Thursday, November 3, 2011 10:24:46 AM
Subject: Re: [jboss-as7-dev] Test Suite Changes



So, the changes to the test suite were based on requirements.  The issues as I see it is that there is no
concensus (making everyone happy) which, in turn, has caused additional changes to the initial pull request[s].

It was anticipated in the requirements discussions, though, that the integration tests would be used for test purposes
other than during a build of AS7.

Thomas, have you looked at the requirements document links mentioned below?  

As far as bugs, fair enough.  They're being addressed as they are uncovered.  JIRAs should be filed.



Shelly



----- Original Message -----
From: "Thomas Diesler" <thomas.diesler at jboss.com>
To: "Darran Lofthouse" <darran.lofthouse at jboss.com>
Cc: jboss-as7-dev at lists.jboss.org
Sent: Thursday, November 3, 2011 9:56:28 AM
Subject: Re: [jboss-as7-dev] Test Suite Changes

Yes, I would also like to see a document that describes how the 
testsuite is (more importantly should be) organised and how to execute 
individual test sections. The document should start with a list of 
requirements.

The argument of "integration-tests.sh makes it easier" is not valid 
IMHO. It is a diversion of an established standard and quite the 
contrary from "makes it easier" IMHO. In short, start with requirements 
and show whether and how they are met and where work still needs to be 
done.

Refactoring the test suite into a clean structure, such that standard 
mvn calls can be used to execute what we need would be the preferred 
solution IMHO.

-thomas

On 11/03/2011 12:40 PM, Darran Lofthouse wrote:
> It would be nice if we could agree which parameters should actually work
> and what they mean - the one that caught me out recently was when
> -DskipTests=true was broken.
>
> Regards,
> Darran Lofthouse.
>
>
>
> On 11/03/2011 11:34 AM, Kabir Khan wrote:
>> Smoke tests are running by default now which is nice. However, a './build.sh clean install -DallTests=true' no longer runs all the tests, while they did last week. This is starting to get very confusing, all I want to do is to process some pull requests and run the tests.
>>
>> If this really needs to keep changing all the time, a this-is-how-we-run-the-tests-today.txt file in the root folder would help :-)
>>
>> On 27 Oct 2011, at 17:20, Ondrej Zizka wrote:
>>
>>> Ok, seems like QA will have to carry the burden of disabling smoke tests whenever they want to run anything else - because Maven's profile activation logic really sucks.
>>> Fixing.
>>>
>>> Ondra
>>>
>>>
>>>
>>> On Thu, 2011-10-27 at 11:36 +0100, Kabir Khan wrote:
>>>> The smoke tests must be run as part of a standard build. Please fix.
>>>>
>>>> If QE have other requirements, which are not possible to combine with the above requirement maybe they should look into using alternate poms or the antrun plugin or something.
>>>> On 27 Oct 2011, at 09:48, Thomas Diesler wrote:
>>>>
>>>>> Currently, the smoke tests don't run as part of the build. Is this really what you want?
>>>>>
>>>>>
>>>> https://hudson.qa.jboss.com/hudson/view/JBossOSGi/job/jboss-as7-master/389/
>>>>
>>>>> -thomas
>>>>>
>>>>> On 10/27/2011 06:17 AM, Stuart Douglas wrote:
>>>>>> I just just merged some changes to the test suite that QE requires for EAP (see below for a link to their requirements). As a result the manner in which the tests are run has changed slightly.
>>>>>>
>>>>>> Due to limitations in maven it is no longer possible to activate all tests using mvn install -DallTests, instead you should use either:
>>>>>>
>>>>>> ./build.sh install -DallTests  - To do a full build with all tests
>>>>>> ./integration-tests.sh -DallTests - To just run all integration tests
>>>>>>
>>>>>> Running individual tests from an IDE or via mvn test -Dtest=MyTest should work as normal.
>>>>>>
>>>>>> Ondej Zizka (in CC) has been the person working on these changes, so if you have any questions or comments he is the person to talk to.
>>>>>>
>>>>>> Stuart
>>>>>>
>>>>>> *
>>>> https://docspace.corp.redhat.com/docs/DOC-74146
>>>>
>>>>>> *
>>>> https://docspace.corp.redhat.com/docs/DOC-69049
>>>>
>>>>>> *
>>>> https://github.com/jbossas/jboss-as/pull/491
>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> jboss-as7-dev mailing list
>>>>>>
>>>>>>
>>>> jboss-as7-dev at lists.jboss.org
>>>>
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>
>>>>> --
>>>>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>>>> Thomas Diesler
>>>>> JBoss OSGi Lead
>>>>> JBoss, a division of Red Hat
>>>>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>>>>
>>>>> _______________________________________________
>>>>> jboss-as7-dev mailing list
>>>>>
>>>> jboss-as7-dev at lists.jboss.org
>>>>
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>>
>>>> jboss-as7-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev