GA meeting in Kranj
On on July 2nd, 2014, General Assembly met in Kranj at a meeting organized by SINTESIO. Scope of the meeting was to discuss about the outcomes of the mid-term review held in Brussels on May 8th, to face the open …
On on July 2nd, 2014, General Assembly met in Kranj at a meeting organized by SINTESIO. Scope of the meeting was to discuss about the outcomes of the mid-term review held in Brussels on May 8th, to face the open …
We are happy to announce that a presentation about the MIDAS Project has been accepted for the ETSI User Conference on Advances in Automated Testing 2014 (UCAAT’14).
On May the 8th, the interim review was taken in the EU Commission in Brussels. The MIDAS Consortium showed the results achieved in the first 18 months and we have received a valuable feedback to improve the expected results for …
On May the 7th, the MIDAS General Assembly met in the Office of Government of Aragon in Brussels, with the objective of integrating the results of the first 18 months of the project to be presented in the review. MIDAS …
On April 29th the General Assembly met in Berlin at a meeting organized by FOKUS. The main objective was to discuss about the demonstrations of the MIDAS v0.2 release which will be shown in the next Review in Brussels. The …
Newsletter number 5 is now published.
The purpose of this document is to introduce, describe and discuss scheduling approaches of test campaigns and approaches to planning of functional, security and usage-based testing. The ambition of the MIDAS consortium is to propose a new framework able to …
This document ‘Libraries for SOA automated test execution’ is part of Work Package 4 ‘SOA automated test execution environment’. It describes the libraries required for functional, interaction and fault tolerance testing, for security testing and generic test components for usage-based …
Deliverable D4.2 Libraries for SOA automated test execution published Read more »
The MIDAS Testing as a Service (MIDAS TaaS) platform is designed and architected according to a SOA-based approach, and provided as an integrated Testing as a Service framework available on demand, i.e., on a self-provisioning, pay-per-use, elastic basis. For this …
The purpose of this document is to refine the requirements we initially defined in D3.1. The major changes concern the tables describing the requirements definitions in D3.1 that have been extended with two additional fields: “implementing modules” and “verification”. The …