1 / 9

Testbed Software Test Plan

Testbed Software Test Plan. I . Mandjavidze on behalf of L. Bobelin – CS SI ; F.Etienne, E. Fede – CPPM ; A. Formica, I. Mandjavidze – CEA/ Saclay. Outline. Motivation and Goal s Proposed Test Strategy Organization Scope Tests of Functionality Pre-requisites Documentation

ebobbitt
Download Presentation

Testbed Software Test Plan

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Testbed Software Test Plan I. Mandjavidze on behalf of L. Bobelin – CS SI; F.Etienne, E. Fede – CPPM; A. Formica, I. Mandjavidze – CEA/Saclay

  2. Outline • Motivation and Goals • Proposed Test Strategy • Organization • Scope • Tests of Functionality • Pre-requisites • Documentation • Deployment • Discussion 2

  3. Motivation and Goals • DataGRID middleware is rapidly evolving • Complex software • Rich in functionality • Stringent schedule of software release plan • Minor releases every two months • Next major release in October, 2002 • Need for continuous test activity • Check for bug-fixes • Validate added new capabilities • Identify eventual « unexpected features » A well-defined systematic approach is necessary 3

  4. Proposed Test Strategy: Organization • Form an independent Test Group within the WP6 • Volunteers from several test (non-production) sites • Close contact with the Integration Team and WPs • For each release • Participate in last stage of integration as an observer • New features and « particularities », initial experience • Deploy and validate at each test site • Examine multi-site operation integrating test sites • Document test results, distribute them within the collaboration • Act after integration and before validation by applications • Give a « green light » to the Validation Team Thorough examination and feedback to middleware WPs 4

  5. Test Strategy: Scope • Installation, configuration • Appreciate required effort, evaluate code portability • Functionality and performance • Check conformance with the documentation • Derive performance figures, identify eventualbottlenecks • Security • Trace for security holes in deployed external packages • Check for non-authenticated and unauthorized accesses, … • Scalability, robustness, fault tolerance, error detection • Operate in distributed multi-user multi-site GRID environment • Operate at high loads, with malfunctioning services, … See draft document on « Testbed Software Test Plan » 5

  6. Test Strategy: Tests of Functionality • Follow layered structure of the DataGRID architecture • Identify interdependency of services • Do not test upper level service iflow-level service is faulty • Determine validation tests for every service • Work is well advanced, see the « Test Plan » document • Develop test suites • Split responsibilities among thetest sites • Depending on expressed interests • Some overlapping is not excluded, might even be necessary • Expect basic tests for services delivered within releases • Correctness of installation and configuration • Basic functionality of services and connection with low-levels Automate test suites when possible 6

  7. Pre-requisites: Documentation • Administration Guide • Download, installation, configuration, maintenance and tests • Detailed description of system-level commands • Users Guide • User environment set-up and test • Detailed description of user-level commands • Developers Guide • Detailed description of available APIs • Per-release updates Good understanding of functionality and services provided 7

  8. Pre-requisites: Deployment • Installation and configuration procedure • Currently extremely tedious and time-consuming • Difficult to keep pace with releases • May quickly discourage Test Group members • Suggestion for major releases • Automate the procedure as much as possible • e.g. self-deployment based on site description • Suggestion for minor releases • Self-extracting patches • i.e. upgrade only concerned parts of middleware Concentrate on functional tests rather than on deployment 8

  9. Discussion • Some open questions • Is the exposed strategy acceptable? • Does the Test Group interfere already during integration? • e.g. from a convenient moment validating Testbed insitu • Would the Integration Team be interested in some test suites? • How long (or short) is an acceptable testing period? • Before providing feedback to WPs, first get one from them • Finalized « Test Plan » document as a basis for discussions • Agreement with the Integration Team and WP representatives • Form the Test Group, share responsibilitiesand … Volunteers? 9

More Related