Bug 90628

Description Dominique Guilbaud 2005-04-07 11:30:22 EDT

Theme 3: Have Hyades naturally integrate with Eclipse SDK use cases

Goal: Allow the JUnit user to have the same experience, once Hyades is
installed, as he/she used to have in Eclipse SDK, with the possibility of
executing his/her JUnit tests in the Hyades framework. Any JUnit test would be
edited and created as usual, and still it would be integrated with other types
of Hyades tests, and could be executed in the Hyades framework (which allows
remote execution, results persistence, and new features to come).

Impacted Projects: The changes required to achieve this step involve the JDT
JUnit plugins (to an extent that needs to be defined). Hyades is also impacted
as a consumer of the JDT JUnit plugins.
As the changes for this phase require phases 1 & 2 to be completed, and as
meanwhile the JUnit features from Eclipse SDK may evolve, no change details will
be listed in this section. This section only lists what problems must be
addressed during this phase.

3.1     Reconcile duplicate ways of achieving a task

3.1.1     New Wizard

Both Hyades and Eclipse SDK provide a way of generating a JUnit test. There are
two separate wizards, with a different UI.
There are pros and cons for keeping only one wizard:
With only one wizard left, there is no confusion about how to create a JUnit test
With two wizards, both the habits of the Java developer and the Hyades tester
are addressed. The first one will be looking in the Java section, while the
latter will be looking in the Test section of the New wizard.
The second solution has been chosen. But the Hyades wizard will share some steps
with the Eclipse SDK one. This is the case for pages that define the JUnit Test
Suite or the JUnit Test Case, which will be the same as the ones used in the
Eclipse SDK wizards. To achieve this step, the JDT team has commited to provide
APIs for being able to reuse these pages (bugzilla 75142).

3.1.2     Launch Configuration

There would be two launch configurations for launching a JUnit test. However,
these launch configurations would drive a completely different execution framework:
The first one is the Eclipse SDK execution framework, which provides a
lightweight, local execution, with volatile results that can be viewed quickly
without requiring any perspective change. This is the favorite launch
configuration for the java developer who is frequently launching JUnit tests
(for test development, regression testing, etc.).
The second one is the Hyades execution framework, which addresses tester
concerns, with batch, versioned management of tests, as it allows all parameters
to be specified  in a deployment file (rather than in a launch configuration),
remote execution, and persistence of test results.
Since the two launch configurations address two different needs, no attempt will
be made to merge them. 

3.2     Automatic migration from plain JUnit to Hyades JUnit

The idea of this change is to avoid requiring the user to import existing JUnit
tests to Hyades before he/she can execute them with Hyades (in other words, make
the JUnit Test Import Wizard unnecessary).
Proposed change: the logical view of the Test Navigator shows plain JUnit tests
as Hyades JUnit Test Suites, even if no Hyades Test Suite is associated to a
given JUnit test. Each time a concrete Hyades Test Suite is required (for
instance, when the user wants to execute it with Hyades), the concrete resource
is generated.