JRA1.1 - EMI-1 Development and Test Plans

EMI-1 Testing Strategy 2 - SEs Access Protocols

This Storage Elements (SE) access protocols 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 : FILE Protocol unit tests (developer focus)
• Scenario 2 : HTTP Protocol unit tests (developer focus)

TBD (Patrick) : Which deployment tests make sense to check file and http on the testbed, hammer-cloud test for dCache on the Testbed

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 :

• 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 :

• Data Area 3 : All storage elements offering support for the http(s) protocol (M12)
• Data Area 4 : All storage elements offering at least a prototype-level support for the "file://" access protocol. (M12)

Testing Environment & Availability

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

• Scenario 1 : FILE Protocol unit tests (developer focus)
  • Unit tests performed on corresponding local machines
    • Responsible : Corresponding PT Leaders

• Scenario 2 : HTTP Protocol unit tests (developer focus)
  • Unit tests performed on corresponding local machines
    • Responsible : Corresponding PT Leaders

Scenario 1 : FILE Protocol 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

• DPM
  • 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

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

Scenario 2 : HTTP Protocol 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

• DPM
  • 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

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