Bugzilla – Full Text Bug Listing
| Summary: | Test Navigator asset versioning to exploit Eclipse Team API's support for logical resources | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Kent D Siefkes <kdsiefke> |
| Component: | TPTP | Assignee: | Bozier jerome <jerome.bozier> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | dkhodges, jkubasta, jptoomey, paulslau, slavescu |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| URL: | http://www.eclipse.org/tptp/groups/Architecture/documents/features/hf_165410.html | ||
| Whiteboard: | closed471 | ||
| Deadline: | 2007-06-30 | ||
|
Description
Kent D Siefkes
The design should be reviewed by the broader project to ensure correctness and extensibility/reusability for the other TPTP models. Use case: -Versioning of test against test logs: a test log is produced against a given version of a test. -> Test log should contain version information about the test. What happens if a part of test is deleted, whereas it is referenced by a test log? Test log references to test assets at time of the test execution and the test assets change over time. (In reply to comment #1) > The design should be reviewed by the broader project to ensure correctness and > extensibility/reusability for the other TPTP models. For example, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=144950. Meeting minutes from Test Project discussion: http://dev.eclipse.org/mhonarc/lists/tptp-testing-tools-dev/msg00870.html Meeting minutes from follow-on AG discussion: http://dev.eclipse.org/mhonarc/lists/tptp-testing-tools-dev/msg00872.html Kent, I would like to clarify the goal of this enhancement. Your initial request was about the 3.2 logical model in Team support. Paul added other use cases regarding the referenced elements under versioning. For instance test log and test. The goal here is to keep track of the version of the test that produced this test log. I would like to clarify which use case you are requesting in order to write the feature description document. Thanks in advance Per our discussion on this topic in today's test meeting, the addition of Paul's test log functionality will be removed from this enhancement and tracked separately. (In reply to comment #2) This request has been removed from this feature and covered under https://bugs.eclipse.org/bugs/show_bug.cgi?id=168421. As such, disregard comments #2, #3 and #4. Updating target to future as requested by the PMC. Enhancements are targeted to future if not in plan for the current release. Providing estimated sizing. Jerome, please provide a description document since this is a candidate enhancement for 4.5. Adding description document link. AG Review Comments: As has been noted in the past, we should fix this in a common way across TPTP and not have a test resource specific solution. Jerome, can you integrate these comments into the Description Document and check in the new version? Thanks. Correcting priority since not a 4.5 candidate enhancement (see http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html). 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. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html). 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. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html). As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. |