JRA1.1 - EMI-1 Development and Test Plans

EMI-1 Testing Strategy 3 - SRM HTTPS Binding Test

This Storage Resource Manager (SRM) compliance 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 : SRM/HTTP Protocol unit tests (developer focus)
• Scenario 2 : SRM/HTTP Protocol tests on Testbed (user focus)
• Scenario 3 : SRM Protocol tests via SRM Communuty Tester (developer focus)

TBD (Patrick) : To be identified Client test scenario should be added

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 2 : Using https instead of httpg for the SRM protocol as a prototype implementation in one storage element and client (library). (M12)

Testing Environment & Availability

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

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

• Scenario 2 : SRM/HTTP Protocol tests on Testbed (user focus)
  • The following components need to be deployed on the testbed for this
    • dCache
    • One Client component

• Scenario 3 : SRM Protocol tests via SRM Community Tester (developer focus)
  • SRM/HTTP Protocol tests on Testbed via SRM Community Tester
  • Link to community tester : TBD (Patrick/Alex) SRM Test Suite Web links
  • The following components need to be deployed on the testbed for this
    • dCache

Scenario 1 : SRM/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

• dCache
  • [UNDONE] Unit test available
  • [UNDONE] Unit test is/can be perfomed regularly

Scenario 2 : SRM/HTTP Protocol tests on Testbed (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

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

Scenario 3 : SRM Protocol tests via SRM Community Tester (developer 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

• dCache
  • Test Description : to be provided when available (link, document, etc.)
  • [UNDONE] Component deployed
  • [UNDONE] Test is/can be perfomed regularly
• SRM Tester (External) used
  • Test Description : to be provided when available (link, document, etc.)
  • [UNDONE] dCache SRM compliance Checked using http(s) instead of httpg