My Projects: Test documents

The testing part of this collection houses three types of documents:

  • test plans

  • test cases

  • test findings

The structure of the site and the navigation over its parts is described elsewhere. What follows here is more about the general contents of these types of documents.

Test plans

This type of document is meant to descibe the intended way of testing one or more parts of the overall functionality. Testing with regards to the individual components can be described with the component.

The following pieces of information are defined:

  • a name

  • a short (single line) description

  • a longer text describing the actual plan

This can reference to functional (user) tasks and processes and data model entities; can be referenced to from test cases and test results

Test cases

This type of document is meant to describe specific situations that are to be tested.

The following pieces of information are defined:

  • a name

  • a short (single line) description

  • a longer text describing the actual testcase

This can reference to test plans; no references from other documents (not even from findings?)

Test findings

This type of document is meant to handle the execution of tests as in reporting failures and describing their solutions. Successes that don't need follow-up can also be described in the associated test cases.

The following pieces of information are defined:

  • a sequence number that is automatically generated

  • a creation date (not shown on screen)

  • an indication of readiness

  • a completion date (not shown on screen)

  • a short (one line) description of the finding

  • a full description

  • room for additional remarks, like the solution

  • the database key of the related action item in the ticket registration (not shown on screen)

  • the action number as shown on the ticket registration screens

This can reference to test plans; no references from other documents