test.txt Quality Management

Scenario

• Create test cases (linked with requirements)
• Create test plans, data sets, etc.
• Assign test cases to practitioners
• Monitor status of test execution
• Create defect reports linked to failed test cases

A test execution tool is used by test practitioners to:

• See work queue of pending test cases
• Claim work, run tests
• Report status & results

The basic integration scenario is that a QM tool drives remote execution of a test execution tool, receiving results & status updates.

Use Cases

1. A QM tool hands task off to a test execution tool to run tests.
2. A QM tool sends instructions to a test execution tool for in-flight tasks (e.g. cancel, pause, resumer, etc.)
3. A test execution tool registers with a QM tool.
4. A test execution tool gets tasks from a QM tool.
5. A test execution tools updates task status while running.
6. A test execution tool posts results when complete.

Status

• Link to whitepaper?
• Link to documentation?
• Link to other outcome resource?

Participants

SteveAbrams? (lead)

Related Links

Mailing List