EMI Integration Test Policy (DRAFT)

This page collects a draft policy for executing Integration Tests of the EMI middleware components. At the moment, this is a very first draft whose main point is to highlight the decisions to be taken. A list of questions are highlighted in bold.

Integration tests are tests involving more than one EMI software component, and may require the involvement of more than one Product Team. The complexity of coordinating and executing these tests varies depending on the components to be tested. Integration tests must be done always after certification and before releasing a component in the production environment.

When a new software component is certified, this has to be installed on the EMI SA2 testbed. The Release Manager must notify the Testbed Manager when a new signed component is available for installation on the testbed. (Q1: Who signed the packages? How?)

When the signed packages are installed in the testbed, some tests should be run: the main goal of these tests is to verify the interaction of the installed component with other components.

Two approaches are possible:

  • Client based: when component A is to be released: and A provides services to component B and component C, B

-- GianniPucciani - 21-Feb-2011

Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 2011-02-21 - GianniPucciani
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback