Bugzilla – Full Text Bug Listing
| Summary: | HTTP tests do not automatically generate JUnit Java code like JUnit tests. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Paul Slauenwhite <paulslau> | ||||
| Component: | TPTP | Assignee: | Paul Slauenwhite <paulslau> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P2 | CC: | ewchan, jkubasta, paulslau, sluiman | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | housecleaned462 | ||||||
| Attachments: |
|
||||||
|
Description
Paul Slauenwhite
Reassign to Test.UI developer - Jerome. After discussion with Julien, he accepts to leverage the sync mechanism that maintains JUnit test and code in sync to HTTP tests. Deferring to i3. Per discussion with Christophe this involves UI changes that cannot be pushed in i3 build (UI freeze). Deferring to 4.3. Reassigning to the component leads to triage for 4.4. Add estimate. This is a rough estimate since it is for UI and I have no UI experience. We would have to find a UI resource to do this. 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. At a minimum, we need to automatically generate the JUnit test class. This defect is important for the usability of the URL test suite editor. As such, increasing the priority so it is considered in 4.5. This is a severe usability issue with one of our consuming products. Reassigning to Duwayne and targeting to 4.5. Duwayne, please complete early in 4.5. Bulk update of the target field to reflect the change in iteration numbers. Bulk update of the target field to reflect the change in iteration numbers. Deferring to I6. Duwayne, I will handle this defect. Including removing the following product doc: Generating an executable test Created attachment 101025 [details]
Generate n Editor Save Partial Patch
Deferring to future as approved by the TPTP PMC (http://dev.eclipse.org/mhonarc/lists/tptp-pmc/msg04926.html). Deferring to 4.5.2 given the lack of resources to complete in 4.5.1. Eugene, should this be a P1 for 4.5.2? Paul, Is this still required and considered sev 1 by consuming product? (In reply to comment #21) > Paul, Is this still required and considered sev 1 by consuming product? > I think that question is actually to yourself since you ahve hte only product shipping this function. ;-) I think the real point is that it is a regular inhibitor to usage. The lack of automation was intended to help show the separation of the definition from the runtine. However as with many TPTP sample tools users are expecting to use them directly. Since this defect requires new strings requiring translation, deferring to the next release of TPTP that will be translated (4.5.3). (In reply to comment #23) > Since this defect requires new strings requiring translation, deferring to the > next release of TPTP that will be translated (4.5.3). > This seems like it should just be a matter of stringing existing actions. Perhaps you can explain to me off line why there is a string issue. I suggest to have the auto code gen in 4.5.2 without any user custom message input support that will introduce any UI dialog, and have a separate defect to enrich the code gen process with user customization interaction in 4.5.3. (In reply to comment #25) > I suggest to have the auto code gen in 4.5.2 without any user custom message > input support that will introduce any UI dialog, and have a separate defect to > enrich the code gen process with user customization interaction in 4.5.3. > Agreed. I will wait to open the second defect once I finish the implementation. Deferring to TPTP 4.5.3 since TPTP 4.5.2 development is closed (http://www.eclipse.org/tptp/home/project_info/releaseinfo/4.5.2/schedule.html) and P2 defects are not considered candidates during release shut-down. As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. Since this defect is more than 2 years old, it may be no longer relevant. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this defect is resolved as WONTFIX. If this defect is still relevant and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. Reopening since still relevant. As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. Since this defect is more than 2 years old, it may be no longer relevant. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this defect is resolved as WONTFIX. If this defect is still relevant and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. Closing. |