Test Modelling Sample Clauses

Test Modelling. In a Model Driven Development approach (see Figure 3-1), the System Under Test must be modelled using models, those models will be of different levels of abstraction and transformations will be used from going from one level to another. Those models will be the input for generating the test cases (this is another kind of transformation: from SUT model to test model). Those test models must be also modelled. Figure 3-1: System Design Models vs. Test Design Models (from [27]) As mentioned previously, one of the most common software development processes is the well-known V model. This model can be extended for the development of the test system: it is called W-model [25], see Figure 3-2. As mentioned in introduction, Model-based design enables new techniques for verification and validation throughout the development process instead of applying the traditional V-diagram process. However, the V-model and W-model are used with the purpose of explaining the role of test modelling in the software development process. SUT models can be described using different languages and notations. For example (see Figure 3-3), UML can be used for SUT models, for specifying the test model the UML testing Profile (UTP) can be used and for execution the TTCN-3 (Testing and Test Control Notation). Figure 3-3: UML focused W-model (from [26]) In this chapter, two of the most used formal test notations for specifying test cases are described: U2TP, UML 2.0 test profile, which provides means to use UML both for system modelling as well as test case specification. TTCN-3, the Testing and Test Control Notation, which is a standardized language to formulate tests and to control their execution. 3.1 UML 2.0 Testing Profile (U2TP)