D.3.3 ALGORITHMS FOR INCREMENTAL ... - SecureChange

Fig. 1. Security Engineering Process
manual test execution or test automation (implementation of keywords). This interaction
process is highly iterative. The model-driven testing process involves three main
roles:
– The Business Analyst is the reference person for the System-Under-Test (SUT) requirements,
business processes and business needs, and he/she communicates with
the Test Analyst to clarify the specifications and testing needs.
– The Test Analyst interacts with the Business Analysts and system experts regarding
the requirements to be covered, and then designs test generation models. He then
uses test generation tools to automatically generate tests and to produce a repository
of test suites that will satisfy the project test objectives.
– A Tester is responsible for (manual) test execution on the basis of the test repository
while a Test Automation Engineer is responsible for connecting the generated
tests to the system under test so that the tests can be executed automatically. The
input for both Tester and Test Automation Engineer is the test repository generated
automatically by the test analyst from the test generation models.
For this process to work smoothly in presence of changes we need to orchestrate the
work of the requirement engineer with the work of the testing engineer. In many cases,
requirements evolution can have impact on a confined part of the system. In such cases
it would be beneficial to clearly identify only those parts of the system that have been
affected by the evolution and that need to be re-tested for compliance with requirements.
In this way re-running all test cases is avoided because it is possible to identify which
new test case need to be added to the test suite and which test cases can be discarded as
obsolete.
2