Bugzilla – Full Text Bug Listing
| Summary: | WI8: Add test execution contextual information to a test log. | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Ruth Lee <ruthdaly> |
| Component: | TPTP | Assignee: | Paul Slauenwhite <paulslau> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P2 | CC: | paulslau |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 74841, 109657 | ||
|
Description
Ruth Lee
Please transfer this defect to the Test.UI.ManualTestClient componet and assign it to paules@ca.ibm.com to include as a work item for feature http://www.eclipse.org/tptp/groups/Architecture/documents/features/hf_74841.html . Add support for adding a the following contextual information to a test case execution result: Defect(s) (e.g. one or more defect numbers for failed test cases). Driver (e.g. product build date or driver number). Tester(s) (e.g. one or more testers). Platform(s) (e.g. one or more execution platforms either programmatically set of set by the tester) Note: This defect covers work item 7 of enhancement #74841 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=74841) to provide a RCP/SWT- based Manual Test Client to replace the existing Swing-based Manual Test Client. P1 Cannot ship without this enhancement normal A problem making a function difficult to use but no special work around is required This feature will be added to the new RCP/SWT- based Manual Test Client. However, this function will not be provided for the remaining TPTP test types since there is no tester as such to determine defects and the testers do not cause a inconclusive/failure verdict for the automated test types. However, capturing the platform and driver information would be relevant for the automated test types. As such, this information will be have to be added to the common execution harness. I should have opened this as an enhancement; sorry about that. (In reply to comment #2) CORRECTION: This is work item #8. (In reply to comment #5) You did! However, this is a defect since it is a work item of enhancement #74841. [Comment by Ruth Lee] I hadn't thought about the automated test types; you're right that we wouldn't need a tester name, unless we wanted to know that it was automated? The tester name could literally be "automated" and pre-filled in? Harm has decided that adding a 'configuration' type of test case to each TPTP manual test suite in the test-results module is the best approach to solve this defect. For example, the description of the 'configuration' type of test case would ask the tester to enter the following information in a structured format in the 'Information' field of the Manual Test Client: Driver (e.g. product build date or driver number). Tester(s) (e.g. one or more testers). Platform(s) (e.g. one or more execution platforms either programmatically set of set by the tester) We will create a single 'configuration' type of test suite and add an invocation to the behavior of each TPTP manual test suite in the test-results module. Since we have already started the TPTP v4.1 (i2) test pass and committing a mass changed to all TPTP manual test suites in the test-results module may introduce a delay in the test pass in the event of an error, we will wait and do this change for the TPTP v4.1 (i3) test pass. As such, updating the target and severity. Cannot contain in TPTP V4.2.0 (i3). Based on priority and available resources, this defect is being considered for deferral from 4.3. If you object to this deferral, please provide a comment ASAP explaining the reason that you need this in 4.3 and we will take that into consideration. Retargeting to 4.4 as decided in today's AG call (only permitting blocking and critical defects in 4.3 i3). Targeting to future since cannot be contained in 4.4. Targeting to future since cannot be contained 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. In TPTP 4.5, the Manual Test type was moved from a General Availability (GA) component to an As-Is component. As-Is components are primarily provided for prior users but imply no support (for example, defects, news group, and mailing lists) or commitment to triage or resolve opened defects. For this defect to be considered, please re-open with an attached patch including code to resolve the symptom and test cases to test the fix. 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. |