Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 330125

Summary:

Split up the org.eclipse.jst.j2ee.tests.bvt.AutomatedBVT into several test suites

Product:

[WebTools] WTP Java EE Tools

Reporter:

Roberto Sanchez Herrera <shr31223>

Component:

jst.j2ee

Assignee:

Roberto Sanchez Herrera <shr31223>

Status:

RESOLVED FIXED

QA Contact:

Chuck Bridgham <cbridgha>

Severity:

normal

Priority:

CC:

ccc, jasonpet, jsholl

Version:

unspecified

Flags:

cbridgha: review+

Target Milestone:

3.2.3

Hardware:

OS:

Windows XP

Whiteboard:

Attachments:

Description	Flags
Split up the AutomatedBVT and allow to select which suites to run	ccc: iplog+

Description Roberto Sanchez Herrera

2010-11-12 13:36:04 EST

Build Identifier: M-3.2.3-20101104214751

org.eclipse.jst.j2ee.tests.bvt.AutomatedBVT has been disabled for a while(see bug 262285).  It needs to be split up into several smaller ones and enabled for the build.

Reproducible: Always

Comment 1 Roberto Sanchez Herrera

2010-11-12 16:29:40 EST

Created attachment 183047 [details]
Split up the AutomatedBVT and allow to select which suites to run

This patch divides the AutomatedBVT bucket (which is very large) into smaller buckets. The proposed classification is:

1 = EJB Bucket
2 = Web Bucket
3 = Enterprise Bucket
4 = Core infrastructure Bucket
5 = Model Provider Tests
6 = Extended Model Provider Tests  

The following is the list of suites currently included in the AutomatedBVT suite. The number in the left of each row is the number of the bucket to which the suite is moved (this list was taken from the class org.eclipse.wtp.j2ee.headless.tests.plugin.AllPluginTests)

1   addTest(org.eclipse.wtp.j2ee.headless.tests.ejb.operations.AllTests.suite());
2   addTest(org.eclipse.wtp.j2ee.headless.tests.web.operations.AllTests.suite());
3   addTest(org.eclipse.wtp.j2ee.headless.tests.jca.operations.AllTests.suite());
3   addTest(org.eclipse.wtp.j2ee.headless.tests.ear.operations.AllTests.suite());
3   addTest(org.eclipse.wtp.j2ee.headless.tests.appclient.operations.AllTests.suite());
3   addTest(org.eclipse.wtp.j2ee.headless.tests.utility.operations.AllTests.suite());
4   addTest(org.eclipse.wtp.j2ee.headless.tests.j2ee.operations.SourceFolderUpdateTest.suite());
4    addTest(org.eclipse.jst.j2ee.tests.modulecore.AllTests.suite());
5    addTest(JEE5ModelTest.suite());
5    addTest(JEE6ModelTest.suite());
    // model provider
5    addTest(ModelProviderTest.suite());
6    addTest(AnnotationProviderTest.suite());
4    addTest(org.eclipse.jst.j2ee.dependency.tests.AllTests.suite());
4    addTest(org.eclipse.jst.j2ee.classpath.tests.AllTests.suite());
4    addTest(WebAppLibrariesContainerTests.suite());
4    addTest(DefectVerificationTestsSuite.suite());
4    addTest(HeaderParserTests.suite());
6    addTest(AllAnnotationModelTests.suite());
6    addTest(MergersTestSuite.suite());

This patch also includes a new properties file, with properties that enable which suites will be run by the ant targets.
 
The testHOLD.xml now includes a target for each of the new suites and one target for all the BVT. Which targets will run depends on the properties defined in the file bvt.properties. (Currently, the properties are set so ALL the suites are executed).

Comment 2 Jason Sholl

2010-11-15 13:51:43 EST

Looks good.  It will be great to have the tests up and running again on builds..  Code checked into both 32M and HEAD for 3.2.3 and 3.3 builds.

Comment 3 Chuck Bridgham

2010-11-17 10:47:10 EST

I approve this now.. but we need to keep a diligent eye on the results, and react quickly