Technical report

4.1.1 End user services

• 
  Test Gen&Run Service, which allows to asynchronously start the execution of a test task (either a test generation or a test execution task), and to actively poll it to inspect the status and the resulting output of any started test task;
  
• 
  Test Method Query Service, which allows end users to list the test methods currently part of the MIDAS portfolio, and to retrieve the properties of any method in the MIDAS portfolio; all its methods are synchronous;
  
• 
  File Management Service, which offers access to the file system private to the tenancy the end user belongs to, and to perform the usual operations supported by a file system.
  

Figure 2: Test as a Service framework as designed and build in MIDAS project.

The TPaaS architecture also provides the Application Program Interfaces (APIs) for the implementation of the Test Method Query Service and the File Management Service.

The Test Gen&Run Service is composed of several services, also referred to as the TaaS core services that contribute to the implementation of the end user test generation and execution functionalities. The core services are not exposed by the TPaaS, but they allow test method developers to implement specific test methods. The Test Gen&Run Service implementations allow end users to use these test methods.

The core services are organised in two levels, as depicted in Figure 2. The first level distinguishes the Test Generation Service from the Test Run Service. While the first service is responsible for automatically generating test cases, test scripts and model transformations for testing, the second service coordinates the run of a specific test cycle, organized in three phases: an optional scheduling phase, a mandatory execution phase, and an optional arbitration phase.

The Test Generation Service is provided by a Test Generation Container. Each container can include different modules as plug-ins, each of them implementing a specific test generation capability, with the same interface of the test generation service. Both Test Gen and Run Services are invoked asynchronously, and their outcome is notified to the Test Gen&Run Service through a notification, whose listener is provided by the Test Gen&Run Service.