Figure 7: Manual Test Design use case

The end user invokes the execution of a test generation and run task with a platform independent non executable representation of the test cases and data as arguments and references them in a TaaS test model. The test cases and data representation and the target SUT must be compatible with the model representation requirements used within TaaS. The TaaS test model is then passed to the TaaS that generates the executable representation of the test cases and data, establishes the connection with the deployed SUT and executes the generated representation of the test cases and data.

As shown in Figure 8, in manual test design end-user scenario, mapping rules are defined by MDSL profile and MDSL to TTCN-3 mapping rules. System models are developed manually based on the test specifications drafted manually. The generation of formal test scripts generated in TTCN-3 language from system models may be supported by data, behavioural fuzzing and/or with the behaviour specifications in terms of sequence of logical messages to (inbound) and from (outbound) the test interface. In addition to the generic process on test suite generation as defined in [ETSI TR 102 840 V1.2.1] and presented in Figure 4, test planning and scheduling models can further refine the generation of the test case sequences. Once the TTCN-3 test cases are generated, the further procedures are equal to direct test execution use case.