Test Script Layer
Principle:
The responsibility of the test script layer is to outline specific inputs and expected outputs for each test case.
A properly designed and implemented ATI layer should result in quite brief and clean test scripts.
In the ideal situation, the test script layer only contains data unique to each test case.
As a result, test scripts rely only on the interface of the ATI and utility layers and this minimizes the refactoring effort in between different releases of the SUT.
These test scripts are written with the help of a unit testing framework in the well-known pattern of
- Set-Up
- Test
- Tear Down
It is important to adhere to the DRY principle.
In case of code duplication, the developer should evaluate whether the extracted duplicate code should actually be part of the functional library layer or if it is rightfully part of the test scripts.
It is highly recommended to choose a unit testing framework that supports tagging and parameterizing test cases.