Community
Participate
Working Groups
The Test Log Viewer displays a link to the deployment used to run the test. In cases where the run use the default temporary deployment named 'default', it hides the link. So far so good. However, the temporary deployment may not always be called 'default' and is certainly the case of my product. I would rather the check be made to see if the deployment object is associated with an eResource which will determine if the deployment is temporary or persisted. I have talked to Bianca nad she agrees.
Not containable in 4.3. Retargeting to 4.4.
Sizing updated as provided by Bianaca.
Targeting to future since not containable in 4.4.
As discussed on this week's Test Project call (January 22, 2007), the Test Project will focus on existing P1 - P2/Blocker - Major and P1/Normal and test creation/automation defects (omitting defects dependant on outstanding features) in TPTP 4.4. All other Test Project defects have been targeted to future. If this defect has been targeted to future and you/originator feel it should be completed in 4.4, please provide the necessary reason as a reply to this comment or a post to the Test Project mailing list (tptp-test-tooling-dev@eclipse.org). We will collectively triage and assess our resources to determine a case-by-case decision.
Correction: The Test Project mailing list is tptp-testing-tools-dev@eclipse.org.
I'm in the same boat as the original submitter of this bugzilla. It is desired for the check to call createDeploymentLinks() to make sure deployment.eResource() != null. This is in class ExecutionResultDetailsPart, method setFormInput. I would like to add that even if not dealing with temporary deployments, this is important in case the deployment file has been deleted. Using base TPTP, if you delete a deploy and open a test that used it. There will still be a hyperlink deployment icon shown in Test Log Viewer. If you click it, an editor opens showing an Exception has occurred. This will always happen if deployment.eResource() == null. So, it's better to check for this condition and not show the deployment link.
Bulk update of the target field to reflect the change in iteration numbers.
Deferring to I5.
Deferring to I6.
Deferring to I7 as discussed by PMC/AG (http://wiki.eclipse.org/TPTP-AG-20080331#Test_Project).
org.eclipse.hyades.test.ui.forms.base.ExecutionResultDetailsPart.java checked in into CVS (HEAD).
Closing by default since not closed by the originator in the 7+ months since being resolved. Please reopen if the issue is still present in the latest TPTP release or the resolution is not correct.
Correcting component.