Defining test properties
You can specify certain information on tests.
See also Viewing a test dashboard.
General characteristics
General characteristics of the test are:
• Name: test name.
• Code: you can assign a code to the test.
• Included in the Initial Plan: this attribute is defined automatically according to plan status at the time of creation of the test. It indicates if the test was present at plan creation, or if it was added later.
• Entity controlled
• Lead Controller: lead controller name.
• Main Control Correspondent
• Objective of the test.
• Category of the test:
• "Compliance"
• "Efficiency"
• Status of the test: this attribute is defined automatically and modified at workflow transitions.
Justification and workload
In this section you can enter the following characteristics:
• Origin: follow-up, specific, recurrent, etc.
• Priority: priorities can be specified for tests. You can select tests to be integrated in the plan based on this priority criterion.
• Estimated Duration (days).
• Estimated Resources
• Estimated Workload
The following characteristics are automatically calculated:• Effective Workload (Hours): calculated from the effective workload defined on time sheets or on activities if no time sheet has been entered.
• Estimated Number of Resources
• Justification of the test
Scope
In this section you can connect process categories or processes to the test.
These can be used to automatically generate the test work program.
For more details, see Completing the work program manually.Milestones
In this section, you can indicate a Planned Begin Date and a Planned End Date. These dates constitute audit milestones.
You can choose to enter milestones at a later stage.Users
In this section you can specify the stakeholders of a test:
• Test Controller: controllers having been previously defined, you can connect but not create controllers. See Assigning resources to tests.
• Person tested
• Other Participant in Test (for information only)
Skills
In this section you can specify the skills required by controllers to execute tests.
To define skills required for the test:
In the Skills frame, click New or Connect to create a skill or connect an existing skill.When assigning controllers to a test, you will be able to compare skills of controllers with skills required for the test. For more details on the report providing this information, see Assigning resources to tests.
Summary
In the Conclusion section, you can specify:
• Key Strengths
• Key Weaknesses
• Evaluation: good overall level, can be improved, etc.
The value specified here is displayed in the test dashboard, at the top of the Characteristics page.Test Activities
A specific page in the properties of the test enables to view test activities.
Deficiencies
A specific page in the properties of the test enables to view deficiencies.