TPTP-Test-Tools-Design-Review-166025-01282008

Date

• January 28, 2008

Attendees

• Present:
  • Jerome Bozier
  • Dawn Peters
  • Alexander Bernstein
  • Paul Slauenwhite
  • Joseph Toomey
  • Kent Siefkes

Background

• Progress update and demo of enhancement 166025 (Move, Copy, Delete, Rename and Import/Export test assets).

• Description Document

• Target: March 14, 2008 (see TPTP 4.5.Detailed Schedule).

Minutes

-Import/export will not be completed. -Demo

• Paul confirmed that the benefit of the logical name for a test asset and determine if it could can be the same as the physical name.
  • Update (January 14, 2008).

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 asserts).
  • Covered under UC5.

Detailed Design

• Detailed Design Document (Microsoft Word).