----- Original Message -----
Sent: Friday, May 28, 2004 5:06 PM
Subject: [hyades-dev] Committer vote
required for M10 check-in
This may be our last set of
requested fixes. I vote yes.
Defect:
bugzilla_64433 -- No messages if testsuite is not attached to remote deployment
Rationale:
The Launch Configuration dialog allows to
choose a Deployment that is not applicable for the selected Test (i.e. the
Test is not contained in an artifact contained in an artifact-location pair
contained in the Deployment). The dialog should present only pertinent
deployments. If the user chooses a non-pertinent deployment, the execution
silently fails.
Risk
Assessment
No
breaking API changes. Low risk change. The fix consists in filtering the
Deployments in the Deployments list by checking that they are pertinent to the
Test.
Dates
fix: May 28
regression test: June 2 (Julien
Canches)
Defect:
bugzilla_64547 -- Launch Shortcuts are not available on Test Suites and Test Cases
Rationale:
In latest Eclipse builds, the Launch Shortcuts
(Run menu) are not available on Test Suite and Test Case nodes in the Test
Navigator. This occurs because the eclipse.core.debug.ui plugin now requires
the underlying element to implement (or be adaptable to) the ILaunchable
interface, in order to enable the Launch Shortcut menu.
Risk Assessment
No breaking API changes. Low risk change. The fix consists in adding an adapter factory for types TPFTestSuite
and TPFTestCase (by declaring it in plugin.xml).
Dates
fix: May 28
regression test: June 2 (Julien Canches)
Defect:
bugzilla_64189 -- problems with 'revert' in
launch config for number of users
Rationale:
The
"Users" tab of URL Test Launch Configuration shows an odd behavior when
playing with the "Apply" and "Revert" buttons. A sequence of clicks can lead
to the impossibility of choosing "1" as the number of users.
Risk Assessment
No breaking API changes. Low risk change. Some refactoring local to the LoadTestUserTab class.
Dates
fix: May 28
regression test: June 2 (Julien
Canches)
Defect
bugzilla_64570 -- Datapool Editor: Need to support the loading of null
datapools.
Rationale:
Although Hyades never loads a null datapool, some consumers of the
control are doing so. This is especially true when consumers are using
the control in a view and always refreshing it with different datapools.
This problem was discovered in a consumer's integration testing.
This fix will not affect Hyades functionality. It simply makes the
control more robust for the consumers. Being able to handle null
datapools is a major usecase for the consumers (an empty one won't do because
they don't want it to be editable).
Risk Assessment:
No API change. Fix is to create a
disabled control when the datapool is null.
Low risk change.
Dates
Target drop date to cvs:
May 28 afternoon EST
Target Regression test: May
28 afternoon EST (Peter Sun)
Target candidate drop:
June 3(pass 3)
Thanks,
--Joe
Joe Toomey
Senior Software Engineer
Rational Software
IBM
Software Group
