Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 330125 - Split up the org.eclipse.jst.j2ee.tests.bvt.AutomatedBVT into several test suites
Summary: Split up the org.eclipse.jst.j2ee.tests.bvt.AutomatedBVT into several test su...
Status: RESOLVED FIXED
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2.3   Edit
Assignee: Roberto Sanchez Herrera CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-12 13:36 EST by Roberto Sanchez Herrera CLA
Modified: 2011-01-10 11:00 EST (History)
3 users (show)

See Also:
cbridgha: review+


Attachments
Split up the AutomatedBVT and allow to select which suites to run (22.12 KB, patch)
2010-11-12 16:29 EST, Roberto Sanchez Herrera CLA
ccc: iplog+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Roberto Sanchez Herrera CLA 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 CLA 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 CLA 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 CLA 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