1. LCG Middleware Testing in 2005 and Future Plans E.Slabospitskaya, IHEP, Russia CERN-Russia Joint Working Group on LHC Computing March, 6, 2006

2. Outline I. Report for 2005 The 4 kind of tests have been developed by Russian developers: 1. Testing of some functionality in LCG-2 Releases ( D.Zaborov, ITEP, L.Stepanova, INR, S.Laptev, INR ) 2. Port SFT tests to gLite ( M.Sapunov, IHEP ) 3. Port new gLite test suites to EDG/LCG Framework ( E.Slabospitskaya, IHEP ) 4. New functionality in gLite test suites ( N.Klopov, PNPI ) II Plans for future (2006 and 2007)

3. Testing of new functionality in LCG-2 Releases (1/3) File Transfer Service (FTS) CLI based test suite 1. A basic test of the ability of the FTS to perform successful file transfer. 2. High level cancellation test implies: - submission of an FTS job with several files to transfer in parallel; - waiting until at least 1 file transfer is done; - canceling the job; - check that files with status "Done" are kept and not deleted; - check that files pending are canceled and not transferred. 3. FTS stress test allows to run many copies of the basic transfer test.. 4. Tests of the reaction of FTS CLI commands to various "mistakes": 5. FTS management tests.

4. Testing of some LCG-2 functionality (2/3) Parsers for Gridftp and Gatekeeper logs Data processing is selecting from logs of gridftp and gatekeeper. Scripts in Perl have developed for these purposes. Results store to MySQL database for future processing. The Perl DBI module provides a generic interface for database access.

5. Testing of some LCG-2 functionality (3/3) Parser for SFT logs Extract old statistics from early SFT history (in PHP4) about good/bad sites and visualization of results ( jpgraph-1.19). - search name of region, and prepare list of regions in html - output image exposes the date statistic for sites into one region (via web browser)

6. Port SFT tests to gLite Site Functional Tests (SFT) Port the existence LGC-2 tests to gLite. gLite SFT consist of 2 main parts: Launcher and Tests. Launcher part has kind of GNU/Linux file structure and consist of 5 main modules. Each module consist of submodules. Main modules called "submit", "status", "publish", "cancel" and "clean". Tests are using "sandbox" feature of gLite/LCG-2 middleware. It is easy to add more tests, rules have been defined..

7. Port new gLite test suites to EDG/LCG Framework I/O storm testing in EDG/LCG Framework This Framework is a set of Testing Suites produced by many of EDG and LCG developers. User launches multiple (parallel or one by one) jobs from User Interface to Worker Node. Each job on Worker Node launches a script which compiles and link C++ program and creates jdl file (this program is a part of job in input sandbox). This C++ program via API creates a file (size is optional) and transfers (writes/reads) these files between WN and I/O server (there and back). The result returns to user (to User Interface). Test creates a local file in temporary directory, copies it to I/O server, and writes it to tmp once again

8. New gLite tests for the functionality different from LCG-2 Direct Acyclic Graph (DAG) CLI based tests (requested by JRA1 team) - create the JDL files for DAG with the regular structure like tree. DAG generation is realized based on the template that defines the Executable and JDL-attributes for three parts of the DAG (pre-jobs, main part and post-jobs) with given number of the levels and nodes. - modify the created DAG structure: add new dependencies or delete the existed ones, based on the appropriate config file. The nodes without dependencies are removed (optional) at the end of this step. - add new JDL attributes (requirements) for the DAG at whole or for one level or for the definite set of nodes according to config file. - run DAG job. - check status of the subjobs during DAG execution. - retrieve the nodes stdout and stderr files after DAG completion and create the log file.

9. Main tasks in 2006-2007 Task 1. "The development of full featured test suites that for the certification of the new grid MW components“ JINR (leading role), SINP-MSU, CERN-IT (consultations) Task 2. "The development of testing procedures focused on special details of various software feature PNPI (leading role), JINR, IHEP, CERN-IT (consultations) Task 3. ”Porting EDG-LCG framework to the gLite environment” IHEP (leading role), SINP-MSU, CERN-IT (consultations)

10. Task 1. Test suites for the certification Certification is a repeatable process of passing numerous functionality, performance and stress tests with the goal to find out the limits of tested software, verify the solidity and functionality advertised. The certification test suites have to allow the verification of correct functionality of each component of the middleware going down to the details of its APIs and command line interfaces (CLIs) where those are available as well as overall functionality involving security and interactions of many different components.

11. Task 2. Test procedures focused on special details The goal of these tests is determination the reason for software failure or its inefficiency. These are *not* stable tests, are changed rather often, and mostly require the collaboration with developers. These are usually tests to find out software problems that are rare, difficult to repeat and as a consequence may need hours having running to get the failure.

12. Task 3. Porting EDG-LCG framework to the gLite Reuse as much as possible existing suites/frameworks/tests from different teams. Minimize duplication of effort when creating new tests. Make sure new tests can be easily incorporated into the existing framework.