2nd Increment – MIDAS Version 0.2

Posted on Posted in MIDAS News

The second increment has the aim to demonstrate the interoperation between the MIDAS modules. To this aim, the consortium will define and statically orchestrate scenarios for the use of MIDAS, based on the three major use cases. For manual test design and direct test execution, one scenario will be defined and orchestrated. For the automated test design, multiple scenarios will be defined, including at least one scenario for (i) functional testing, (ii) security testing, (iii) usage-based testing, and (iv) a scenario that combines at least two different testing approaches. For all the scenarios, sample inputs shall be provided. With MIDAS Version 0.2 these scenarios will only be orchestrated but not fully executable, with the exception of the direct test execution scenario.

The defined scenarios and inputs will also serve as a first look on how MIDAS can be used for the pilot providers in order to start working on concrete demonstration scenarios.

Additionally, the MIDAS DSL format and canonical test case specification will be fully agreed upon between the partners at this point, i.e. the complete input and output formats both between external users of MIDAS and internally between MIDAS modules will be defined. The sample inputs for the statically orchestrated usage scenarios will serve as examples for the finalization of the DSL. An initial input validation for these inputs with respect to the DSL will be performed. The verification will be performed against services that mimic the current state of the pilots and are based on the available pilot WSDLs.

Objectives:

  • Definition of scenarios and sample inputs for the three major MIDAS use cases (automated test design, manual test design, and direct test execution).
  • Full functioning of the direct test execution use case scenarios.
  • Usage of dummy implementations of the pilots based on their WSDLs for the verification.
  • Full agreement on the MIDAS DSL format and canonical test case specification.
  • Integration step 3 as well as the first iteration of integration steps 4 and 5 are completed.