LCG-SPI: SW-Testing LCG Applications Area

1
LCG-SPI SW-TestingLCG Applications Area
LCG Software Process Infrastructure

• GridPP 7th Collaboration Meeting
• Manuel.Gallas_at_cern.ch
• LCG/SPI
• LCG Software Process Infrastructure

2
Outline and Context
3
Overview
4
Test FrameWorks

• Requirements
• Work with different languages (C, Python, )
• Allow two ways of testing test the output of
  the code and test inside the testing-code.
• Easy way to integrate existing tests.
• Allow the creation of dependencies among tests
• Organize the tests by components or packages.
• Regression testing
• Easy integration with the Nightly Building
  System.
• Provide also a graphical interface.

5
Test FrameWorks X-Unit family

• Scope Unit testing
• The same assertion style in different
  languages.
• Provides- The name of the test case that failed.
  
• -The name of the source file that contains the
  test.
• -The line number where the failure occurred
• Different platforms/compilers
  (Linux/Solaris/Windows)

6
Test FrameWorks Oval

• Can be use for Unit-test to Validation tests.
• Compare the output log file with a given
  reference file (Smart comparison of those lines
  which start with Oval)
• It is possible to set different run
  environments.
• Can run external scripts and external binaries.

7
Test FrameWorks QMTest

• Uses a graphical interface for creating and
  running tests
• Runs tests in parallel
• Organizes tests hierarchically
• Supports execution of a single test or many at
  once
• Records dependencies between tests
• Can be run in batch mode -gt easy integration
  with the Nightly-Building systems

8
Test FrameWorks Global picture
9
(No Transcript)
10
User support Web information
http//spi.cern.ch/
11
User support Tools supported

• Different platforms
• (Linux/Solaris/Windows)
• Different compilers
• Integrated with SCRAM
• and ready to be used
• Installed in AFS/DFS
• Instructions to install
• them in a local machine

How to use them ?
12
User support How-To





13
(No Transcript)
14
Sw-Testing policies
http//spi.cern.ch/software_development.html

• Sw-testing policies are
• needed to ensure
• Software is created together
• with the tests.
• Test directory structure and
• naming should be homogeneous
• and this will imply easy life to
• have automatic tools.
• Common and well integrated
• tools

15
(No Transcript)
16
Test Documents

• For all project is needed a Test Plan in order
  to have a clear idea of the type of tests,
  schedule, environment and responsibilities.
• We use a template

17
Conclusions Software testing is an important
task and we have tools in place to do it.

• Thanks to
• PPARC
• LHC experiments
• LCG

Feedback and interaction are always welcome!!