The development process described above is reflected in the workpackage structure of MHP-CONFIDENCE shown in the figure below. Due to the initial availability of test assets in most steps, nearly all WPs start work working in parallel after a startup phase.

WP4 is concerned with implementing the Test Assertions and Strategies produced by WP3 into test software. The work carried out in WP3 and WP4 relies on the analysis provided by WP2. The implemented tests are delivered to WP5 for verification/review for acceptance.

Test implementation work of WP4 has been carried out in separate implementation projects, tasked with development of test software to given specification (assertions/strategies and other requirements, such as integration to the automated test environment, as well as the MHP specification itself).

In order to have a controlled software development process leading to deliverables of high quality, and in order to gain access to developers with MHP application writing experience, subcontractors were used in WP4. This approach allowed the use of MHP-CONFIDENCE partners’ resources on the complex task of verification of the tests against MHP various receivers (WP5).

Test implementation requires deep analysis of the assertions/strategies in order to design the test software. This, and the findings on behavior of MHP platforms when initial test code is executed (experimentally), gives raise to feedback on the correctness and testability of assertions/strategies in an MHP implementation independent manner, given the mechanisms offered by MHP, and the extent to which certain receiver behaviour is specified in the MHP specification.

Additionally, specification issues are discovered during the process. Such issues have been forwarded to DVB project for discussion and solving jointly with MHP-CONFIDENCE. For communication between the WPs of MHP-CONFIDENCE an infrastructure has been developed which is described in more detail here.