Evaluation Methodology based on Test Cases Sample Clauses

Evaluation Methodology based on Test Cases. This section introduces the methodology selected for WP7 in D7.1 [21] to test the IoT6 architecture and the involved components. For the test process of the IoT6 architecture, the selected methodology is ETSI EG-202-237 [23] also used in the PROBE-IT project [24]. The ETSI methodology defines a global process for interoperability testing in distributed systems. This guide indicates the specification and execution of interoperability tests for general communication systems. For the IoT6 project, it needs to adapt this methodology in order to fit the requirements of the IoT6 architecture. This adaptation was done in the deliverable D7.1. Here, we only provide a brief introduction of the testing methodology for a further discussion of the testing topic; the reader is referred to D7.1. The selected methodology takes uses cases (UCs) as a basis to generate Test Cases (TCs) for identifying 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 entire project development cycle from the very start. While in the IoT6 project the testing process just started after initial achievements have been reached, the use cases described in D1.1 are still a very good means to assess the functionality of the entire 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 a 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, where behaviours include interactions between actor and subjects who may result in state changes and communication with the environment. A use case defines how a user interacts with a system to achieve a goal. The user in this part can be a human being, or another system component. Use cases are made up of one or more use case scenarios, which describe paths which can be followed. A Test Case (TC) is a set of inputs in combination with execution conditions and expected results, developed to execute a specific program part to verify a particular requirement. A Test Case is a set of inputs that exercises...