[HARMONY-3633] [testing] JEdit automated GUI test scenario for B&T 2.0 infrastructure

• Type: Test
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Component/s: build - test - ci
• Patch Info: Patch Available
• Estimated Complexity: Novice
• Assignee: Stepan Mishura
• Reporter: Vladimir Molotkov
• Created: 12/Apr/07 08:36
• Updated: 02/May/13 02:29
• Resolved: 25/Jun/07 04:52

Description

I've created automated test scenario for application-oriented (using JEdit application) DRLVM testing. The scenario should be integrated into new build-test infrastructure proposed in the

https://issues.apache.org/jira/browse/HARMONY-3501

The scenario starts JEdit application on tested JRE and invokes typical for Java development sequence of actions in it. Tested JRE can be specified using test's 'parameters.xml' file.

The bundle contains sources required for building the executables, test setup and run. The files in the bundle should be placed into adapters/ and tests/ directories proposed in new BT infrastructure. Just unzip the bundle into the root dir of the new buildtest and follow instructions in README in the HARMONY-3501.

Issue Links

• depends upon: HARMONY-3501 BT Infra Improvement
• relates to: HARMONY-3260 [classlib][swing] Can't draw JTable's cell with custom cell renderer
• relates to: HARMONY-4411 [ibm vme][kernel][jedit] ClassLoader.getSystemResource() returns URL with null host
• relates to: HARMONY-4635 [classlib][awt] Toolkit.setLockingKeyState() is not implemented on Linux
• relates to: HARMONY-4636 [classlib][awt] Toolkit.getLockingKeyState() is not implemented on Linux
• relates to: HARMONY-4423 [classlib][awt][jedit] Toolkit.getLockingKeyState() is not implemented
• relates to: HARMONY-4503 [classlib][awt] Toolkit.setLockingKeyState() is not implemented
• relates to: HARMONY-4659 [testing] JEdit automated GUI tests use obsolete workaround for java.awt.Toolkit