Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

TPTP-Test-Tools-Design-Review-162605-12042007

Revision as of 17:35, 4 December 2007 by Dmorris.us.ibm.com (Talk | contribs) (Minutes)

Date

  • December 4, 2007

Attendees

  • Present:
    • Paul Slauenwhite
    • Duwayne Morris
    • Kent Siefkes
    • Joe Toomey
    • David Chadwick

Background

  • AG review of enhancement 162605 (Test execution should support parallel execution of tests).

Minutes

Starting over now, I accidently hit the save button after the Wiki timeout and lost what I had written.

There are two functional aspects of this feature:

  • 1. Execute multiple tests concurrently from the same Host IDE session.
  • 2. Launch and execute a test on a large number of agent machines.

As Joe explained during the call, it was previously the case that launching concurrent multiple tests was supported in TPTP. For example, while running a manual test, the user could launch a JUnit test that would run in parallel. There were failures under certain conditions. As a result, a decision was made to lock out this functionality to improve product reliability. Scott Schneider documented was done and the problems encountered in 106852.

As a part of this enhancement, the direction is to restore this functionality, write automated tests to guard against regression, and fix the defects that are causing problems/failures.

The second issue is the major force behind this enhancement. A consumming product requires TPTP support to launch perhaps 50 agent machines in parallel as opposed to the current implementation, which is in serial. The issue is that the combination of initializing the agent, starting the session JVM, deployment of needed files via TPTP file transfer service, and starting the test runner is all done sequentially per agent. As a result, a run using 30 agent machines may take perhaps 45 minutes to initialize before starting test execution.

Action items

Back to the top