Jump to: navigation, search

TPTP-Test-Tools-Design-Review-166025-01112008

Date

  • January 11, 2008

Attendees

  • Present:
    • Alexander Bernstein
    • Duwayne Morris
    • Paul Slauenwhite
    • Jerome Bozier
    • Kent Siefkes

Background

  • Continuation of the October 25, 2007 review of enhancement 166025 (Move, Copy, Delete, Rename and Import/Export test assets).

Minutes

  • Since Jerome is 50% on TPTP, Paul will cover his defect and testing responsibilities so he can dedicate all of his 'TPTP' time on this enhancement.
    • We need to be code/testing complete on enhancement by the end of I6 development (March 14 - see TPTP 4.5.Detailed Schedule), leaving 9 weeks or 180 PH for completing this enhancement.
  • Paul confirmed that there are cases in the other TPTP models (log, trace, and statistical) that do use references between resources. For example, the references between monitors/nodes/processes/agents in the trace model.
    • Marius also thought RPT was held references from statistical to Common Base Event resources.
      • Kent confirmed that this was not supported.
    • We will reuse the existing implementation provided by Jerome G. but the implementation should should be generic for all TPTP models (test, trace, log, and statistical).
  • Jerome B. has ported the code implemented by Jerome G. from 4.3 to 4.5.
    • This code requires the user cases to be performed in the Test Perspective/Test Navigator.
    • This code handles the delete, move, and rename use cases in the Test Navigator but requires the copy/paste and import/export use cases.
    • Some minor bugs exist.
    • Substantial testing is required.
  • References requiring updates exist between:
    • test logs -> test suites
    • deployment -> artifact and location
    • artifact -> datapool

Core Use Cases

  • UC1. Move:
    • Move a referring or referenced test asset to another directory.
    • Requires update of references in the referring test asset(s) when moving the referenced test asset.
    • Requires update of references in the referring test asset when moving the referring test asset.
    • Currently supports a move via the Refactoring wizard but must support cut/paste and drag/drop.
  • UC2. Delete:
    • Delete a referring or referenced test asset.
    • Requires deleting references in the referring test asset(s) when deleting the referenced test asset.
    • Requires a deep deletion (confirmed by the user), which deletes all referenced test asset(s) (e.g. deleting all test logs if a test suite is deleted) when deleting the referring test asset.
  • UC3. Rename:
    • Renaming a referenced test asset.
    • Requires update of references in the referring test asset(s) when renaming the referenced test asset.
    • Physical versus logical renaming:
      • Need to confirm the benefit (if any) of the logical name for a test asset and determine if it could can be the same as the physical name.
  • UC4. Copy/paste:
    • Copy a test asset to the same or another directory.
    • Requires regeneration of the IDs in the test asset.
    • Potentially requires renaming the test asset (e.g. copy/paste in the same directory) - see UC3.
    • Potentially requires moving the test asset (e.g. copy/paste in a different directory) - see UC1.
    • Physical versus logical renaming:
      • Need to confirm the benefit (if any) of the logical name for a test asset and determine if it could can be the same as the physical name.
  • UC5. Error handling:
    • Fall-back error handling for modifications done outside of the Test Perspective/Test Navigator (e.g. deleting a referenced test asset on the local file system).
    • Iterates the workspace when the Test Perspective/Test Navigator is opened to correct any inconsistent references/names.
  • UC6. Import/export:
    • Export a subset of test assets and then importing the subset of test assets into a new workspace (e.g. missing test assets).
    • Covered under UC5.

Detailed Design

Action items

  • Jerome will schedule a follow-on call/demo for the week of the January 28 - February 1, 2008, including Joe and Dawn.
  • Paul will confirm the benefit (if any) of the logical name for a test asset and determine if it could can be the same as the physical name.