Bugzilla – Full Text Bug Listing
| Summary: | Properly created test launch configurations display an error when reselected in the launch window | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Joe Toomey <jptoomey> | ||||
| Component: | TPTP | Assignee: | Nédélec Patrick <nedelec> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P1 | CC: | amehrega, kevin.p.o'leary, paulslau | ||||
| Version: | unspecified | Keywords: | plan | ||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 156858 | ||||||
| Attachments: |
|
||||||
|
Description
Joe Toomey
*** Bug 160565 has been marked as a duplicate of this bug. *** Adjusting priority -- this is a regression and belongs to a very common use case. Please target to 4.4 since all non-blocking/critical defects will be deferred as decided in today's AG call. *** Bug 164846 has been marked as a duplicate of this bug. *** Raising severity to reflect duplicate's severity. Reassigning to the component leads to triage for 4.4. Unable to reproduce with TPTP-4.4.0-200701220100 build version: Create a manual test and a deployment, use the launch configuration dialog as mentioned. The message is not displayed and the last configuration well validated. Updating hours worked I still see this bug very frequently. It doesn't happen in the simplest case where you create a single launch config and then try to reuse it, but it happens in many other normal use cases. I'll describe one way to reproduce this: In an empty workspace with a clean configuration, import the attached psf file (Import Team project set, anonymous user). The project contains 6 persisted launch configuration files (note that this problem is not limited to .launch files, but this is an easy way to reproduce.) Open the Run dialog and expand the Test tree to see the 6 launch configurations. Click on any one of them and see that an error is displayed saying that there are no deployments available for the selected test. Note also that no test is selected. If you modify the launch configuration in the dialog so that it matches what was stored (selecting the same test, deployment and location that was stored in the launch config before), the apply and revert buttons become grayed out (because there is technically no change to the launch config, although there is no longer an error listed and the test can be run now. Note that I made some additions to this dialog late in i2 (and still need to disable the "database" option if a debug flag is not set.) This is not the cause of the problem I describe above. The same steps result in the same failure with earlier i2 and i1 builds. Please let me know if you have trouble reproducing this and we can do a netmeeting. Thanks. Created attachment 61823 [details]
Team Project set for TestServices test project
This is set for pserver access, so you need to use anonymous, not your real eclipse login
Fix completed: The Junit proxies hierarchy is now well managed by the TestProvider. Reporter: Please verify and close in preparation for shutting down the TPTP 4.4 release. Thanks. Verified in 4.4. Closing. |