Component View
The long-term goal of the test execution engine is to set up a potentially complex target test environment based on the analysis of the corresponding network service graph. However, the scope of this first release is to deploy onto a pre-existing test deployment. Therefore the current version of the test execution engine focuses on the gathering of the network service metadata from the SP in order to run the relevant test plugin and gather the corresponding results. An outline of the position of the TEE is given below
Workflow
The workflow below outlines how the tee currently prepares and runs the tests on the target SP. In this simplified version the configuration manager can presuppose that the test probes are configured correctly and therefore can focus on the configuration of the Tester Plugin (Steps 2-5). The implementation of the test execution via docker is used as an alternative to utilizing a REST API for the initial release. Finally the storage of the test result in Step 9 is directly passed back to the calling entity for external presentation.
