Software Testing for Distributed Systems‌ Testing with Use Cases and Test Cases Sample Clauses

Software Testing for Distributed Systems‌ Testing with Use Cases and Test Cases. The approach to take uses cases (UCs) as a basis to generate test cases (TCs) is promising to launch the testing activities in a project at a very early stage of the development cycle. The advantage of this method is that the generation of test cases can begin before a single line of code is written and as a result the testing activities can accompany the whole project development cycle from the very start. While in the IoT6 project the testing process just started after initial achievements have been reached, the UCs described in deliverable D1.1 are still a very good opportunity to assess the functionality of the whole system and to create test cases in spite of components that are not yet fully developed. A UC is therefore defining the behaviour of a system, without necessarily referencing the internal structure, thus it can be seen as black-box approach. It can be used to model the external requirements on a subject (i.e. component) and further specify the functionality exposed by a subject. The focus lies on specifying behaviour that a subject can perform with one or more actors, while behaviours include interactions between actor and subjects which may result in state changes and communication with the environment. The creation of test cases is a basic step for software testing in any domain, as test procedures can be constructed from test cases from test automation, test scripts may be implemented. One aspect of test cases is the identification of conditions which have to be implemented and are necessary to verify the system requirements. As previously mentioned, TCs can be created as soon as the UCs are available, as for their generation only the external requirements are necessary. The most important part of a UC for generating TCs is the flow of events [6]. A typical UC consists of the basic flow, which more or less describes, what usually happens when the UC is executed and the alternate flow of events, which corresponds to the behaviour of exceptional- and optional events relative to the basic flow. In the presented scenarios for the IoT6 architecture, the usual flow of events was modelled, while in scenario 2 an optional flow is included for demonstration purposes. Use case scenarios are instances of a UC or in other words a complete path from start to termination of the UC. They may be seen as the basis for the creation of TCs. A test case (TC) is a set of inputs in combination with execution conditions and expected results, developed to exec...