JRA1.1 - EMI-1 Development and Test Plans

EMI-1 Testing Strategy 1 - GLUE2 Information

This GLUE2 Information testing strategy is about decisions of how we are going to approach the testing in terms of people, tools, procedures and support.

One idea is to continously improve our plan together with SA2 and SA1 if necessary.

Overview

Testing Stage & Scenarios
We have identified the following types of testings to be undertaken :

• Scenario 1 : GLUE2 information retrieval unit test (developer focus)
• Scenario 2 : GLUE2 information retrieval testbed tests (user focus)

Date/Time
Scheduled for :

• 01.12.2010 - 28.02.2010 - Testings performed randomly in this period

Participants
We have identified the following individuals that will be involved in the testing :

• Laurence Field (for providing the general testing framework)
• PT leaders of the components involved (for developing/integrating tests in their component)
• JRA1.8 Task Leader (for continous quality check)
• JRA1 Leader (for checking the acceptance criteria to get components in EMI-1 Release)

Technical Objectives
The following EMI technical objectives are verified with this test strategy :

• Compute Area 1 : Glue 2.0 support in job management services and client tools (M12)
• Data Area 1 : All storage elements publishing initial GLUE 2.0 storage information and one storage client (library) is capable consuming that. (M12)

Testing Environment & Availability

IT Environment
We have identified the following details of the environment to be used for testing per scenario:

• Scenario 1 : GLUE2 information retrieval unit tests (developer focus)
  • Unit tests performed on corresponding local machines
    • There is one test functionality available that may be used among many components : gstat validation tool [ More Details ]
    • Unit test based on python exists and was extended to support GLUE2 in parallel to GLUE1.3
    • Link : https://tomtools.cern.ch/fisheye/browse/IS/gstat-validation
    • initial version of validation tool for GLUE2 available
    • Responsible : Laurence Field and corresponding PT Leaders

• Scenario 2 : GLUE2 information retrieval testbed tests (user focus)
  • Tests performed on the EMI Testbed using relevant components
    • EMI Testbed of relevant components need to be on the EMI Testbed as services/tools
    • The following components will be required :
      • A-REX
      • WMS
      • CREAM
      • UNICORE-BES
      • DPM
      • STORM
      • dCache
      • lcg_util (including GFAL)
      • ARC* Client (including libarc_client)
      • UCC Client (including BES plugin)

Scenario 1 : GLUE2 Information retrieval unit tests

Here we describe the situation we need to test and their corresponding actions per components :

Situation

Unit tests & components
These unit tests should be continously performed and being ready by end of 2011-01 to be JRA1-internally tested during 2011-02

The ETICS QA Tab can be used and the reports should be uploaded to the following wiki page : TBD : Wiki page 1.8

• A-REX
  • Test Description : to be provided when available (link, document, etc.)
  • [UNDONE] Functional test available (2010-10-29, Oxana)
  • [UNDONE] Unit test is/can be perfomed regularly

• WMS
  • Test Description : to be provided when available (link, document, etc.)
  • [UNDONE] Test is not available yet (2010-10-29, Marco)
  • [UNDONE] Unit test is/can be perfomed regularly

• CREAM
  • Test Description : to be provided when available (link, document, etc.)
  • [UNDONE] Unit test available
  • [UNDONE] Unit test is/can be perfomed regularly

• UNICORE-BES
  • Test Description : to be provided when available (link, document, etc.)
  • [UNDONE] Unit test available
  • [UNDONE] Unit test is/can be perfomed regularly

• DPM
  • Test Description : to be provided when available (link, document, etc.)
  • [UNDONE] Unit test available
  • [UNDONE] Unit test is/can be perfomed regularly

• STORM
  • Test Description : to be provided when available (link, document, etc.)
  • [UNDONE] Unit test available
  • [UNDONE] Unit test is/can be perfomed regularly

• dCache
  • Test Description : to be provided when available (link, document, etc.)
  • [UNDONE] Unit test available
  • [UNDONE] Unit test is/can be perfomed regularly

Scenario 2 : GLUE2 information retrieval testbed tests (user focus)

Here we describe the situation we need to test and their corresponding actions per components :

Situation

Testbed setup & components
These tests should be continously performed during the implementation based on relevant milestones and intensively tested during 2011-02

• A-REX
  • Test Description : to be provided when available (link, document, etc.)
  • [UNDONE] Component deployed
  • [UNDONE] Test is/can be perfomed regularly

• WMS
  • Test Description : to be provided when available (link, document, etc.)
  • [UNDONE] Component deployed
  • [UNDONE] Test is/can be perfomed regularly

• CREAM
  • Test Description : to be provided when available (link, document, etc.)
  • [UNDONE] Component deployed
  • [UNDONE] Test is/can be perfomed regularly

• UNICORE-BES
  • Test Description : to be provided when available (link, document, etc.)
  • [UNDONE] Component deployed
  • [UNDONE] Test is/can be perfomed regularly

• DPM
  • Test Description : to be provided when available (link, document, etc.)
  • [UNDONE] Component deployed
  • [UNDONE] Test is/can be perfomed regularly

• STORM
  • Test Description : to be provided when available (link, document, etc.)
  • [UNDONE] Component deployed
  • [UNDONE] Test is/can be perfomed regularly

• dCache
  • Test Description : to be provided when available (link, document, etc.)
  • [UNDONE] Component deployed
  • [UNDONE] Test is/can be perfomed regularly

• lcg_util (including GFAL)
  • Test Description : to be provided when available (link, document, etc.)
  • [UNDONE] Component deployed
  • [UNDONE] Test is/can be perfomed regularly

• ARC* Client (including libarc_client)
  • Test Description : to be provided when available (link, document, etc.)
  • [UNDONE] Component deployed
  • [UNDONE] Test is/can be perfomed regularly

• UCC Client (including BES plugin)
  • Test Description : to be provided when available (link, document, etc.)
  • [UNDONE] Component deployed
  • [UNDONE] Test is/can be perfomed regularly

Tracking

• 2011-02-03 - initial version of gstat validation tool ready and page updated