Technical report
Download 5.82 Mb.
|
- Navigate this page:
- Automated Test Design
- Figure 3: End user main use cases.
- Figure 4: Process for model-based testing with system models.
5 End user use casesIn a deeper manner, the core TaaS functionalities can be described through end user use cases, specifically: Direct Test Execution, consisting in the execution of TaaS-compliant legacy TTCN-3 (Testing and Test Control Notation) test suites; Manual Test Design, consisting in the execution of test cases and data provided in a non-executable and platform independent model; Automated Test Design, consisting in the automatic generation of test cases and data, and their execution. They are sketched briefly in Figure 3 with the additional use case Identity & Authentication used to check that each end user is a registered user of that tenancy, and it is authenticated before invoking the capabilities of that tenancy. The authentication, in general, will be propagated to the whole TaaS architecture to identify and authenticate the end users with the other tenancy services, as well as with TaaS core services. As this aspect represents a cross-cutting concern among all TaaS services, it is included and used automatically in all end user use cases. 
Figure 3: End user main use cases. Manual test design and automated test design are inline with the process for model-based testing with system models as defined in [ETSI TR 102 840 V1.2.1]. In both cases, the generation of executable test cases is generated from System models, which can either be developed manually based on the system requirements or automatically generated from the implementation under test. This process is actually further enhanced by combining the test generation process with the usage based testing, data and behavioural fuzzing and test scheduling heuristics. 
Figure 4: Process for model-based testing with system models. Download 5.82 Mb. Share with your friends:
|