02 - Execution
Objectives
- Performed tests for registered systems
Pre-requisites
- Test Session is configured and opened
- Participants are registered
- Systems are registered
- Systems configurations are ready to exchange informations
- Tests are ready, validated and assigned
Inputs
- Key Performance Indicators that allow following the progress of the test execution
- Reporting elements that need to be provided in the test session report
- Satisfaction questionnaire for participants are prepared
Actions
- Test Session Manager
- Sends Kick-off mail (see template)
- Consults KPI
- Turns critical status to on
- Grades systems
- It is possible to add some test case to the test plan, even if they are not planned at the beginning.
- SUT Operators
- Run assigned tests
- Store any proof of test execution (logs, trace...)
- Change tests status
- Complete the satisfaction questionnaire
- Monitors
- Verify assigned tests
- Specific attention must be paid at the moment a test result seems to be false : monitor checks environment first after concluding if the result is false or not
- in case of Test steps are not performed (eg : NIST tools not available), monitor mentions it and adds a comment on the reason why it is not impacting the test result.
- Complete the satisfaction questionnaire
Outputs
- Satisfaction questionnaires, see for example the Istanbul survey
- Set of test instances performed during the Test Session execution (includes Monitors and SUT operators comments)
Tools
Flowchart
Kick-off mail template
CONTEXT (SUT Description)
- List of organizations / SUTs / SUT Operators :
- On Gazelle Test Management : in "Connectathon" -> "Find systems" to view organizations, systems and SUT Operators concerned by the Test Session.
COVERED BY 17025 ACCREDITATION ?
TEST SESSION IDENTIFICATION
- Test session name :
- If on line session :
- Risks :
- Begin :
- End :
- Test Session Manager :
- Monitors :
- On Gazelle Test Management : in "Connectathon" -> "Find a monitor" to see all monitors concerned by the Test Session
- Quality controller :
TEST PERIMETER
- Tests to run :
- Tests to run are provided by the Gazelle Test Management Tool
- Test not to run :
- Configurations :
- Number of configuration :
- Configuration identification :
ENVIRONMENT
- Gazelle Platform :
- Other Test Tools :
- [TEST TOOL 1] version :
- [TEST TOOL 2] version :
- [TEST TOOL 3] version :
SPECIFIC REQUIREMENTS
- Requirement 1 :
- Requirement 2 :