ETSI - TS 101 207-2
Identification Card Systems; Telecommunications IC Cards and Terminals; Test Methods and Conformance Testing for EN 726-7; Part 2: Test Suite Structure and Test Purposes (TSS&TP)
| Organization: | ETSI |
| Publication Date: | 1 July 1997 |
| Status: | inactive |
| Page Count: | 83 |
scope:
The present document provides Test Suite Structure and Test Purposes (TSS&TP). It applies to the Security Module (SM) defined in EN 726-7 [9] in compliance with the relevant requirements, and according to the relevant guidance given in ISO/IEC 9647-7 [14] and ETS 300 406 [12].
The set of test purposes described herein is intended to proof the compliance of a security module with the standard EN 726-7 [9] (about 140 tests) and it is seen as an extension of the test purposes made for TS 101 200-3 [8] (about 645 tests), however the number of tests and the depth of testing is not sufficient for a product qualification test.
For a product qualification at least the following tests should be added:
- User profile test
To test whether the SM suits the need for a specific application. Here all possible scenarios should be run.
- Life cycle test
To test the behaviour of a SM after it has been used for X transactions, where X is a multiple of the guaranteed life cycle of the programmable memory.
- Stress test
To test the behaviour of the SM at physical stress, such as under voltage, over voltage, too high or low frequencies and spikes on the VCC/VPP line.
- Performance test
To test whether the implementation is able to handle the defined scenarios within the defined time limits.
- Key test
Each key in a SM should be used for its specified purpose at least once and the result should be checked.
- Additional file tests
Each file present in the SM should be selected and read out, if possible. The answer to SELECT and the contents of the file should be checked against the specification.
Tests for additional functions
For a compliance with the specification the SM should at least be tested with:
- each allowed parameter, or at least their extreme values;
- at least one invalid parameter;
- each return code should at least be provoked once;
- the successful operation of the function should be tested.
In addition to that, tests can be added for:
- all invalid parameter combinations;
- undefined situations; etc.
Document History
