README файл для тестового набора OLVER

This file describes the process of building and launching test set.
If you have installed the compiled version of test set,
you can skip "test building" section.

All necessary commands are given relative to root directory of the test set
In case of compiled package it is /opt/lsb/test/olver-core.


  1. Requirements for software and hardware
  2. Building test set
  3. Running tests
  4. Generating test report
  5. Browsing test results
  6. Possible troubles with building

  1. Requirementes for hardware and software

    OLVER Core test set supports IA32, IA64, x86_64, s390, s390x, PPC32, PPC64 architectures.

    The following list contains Linux distributives, that were used for test running. All detected errors in standart and realization were documented and put to database of known errors:

    • Debian GNU/Linux 4.0 (etch) IA32, IA64 architectures.
    • Debian GNU/Linux 5.0.3 (lenny) x86_64 architecture.
    • Moblin release 2.0 IA32 architecture.
    • Moblin release 2.1 IA32 architecture.
    • openSuSE 11.2 x86_64 architecture.
    • RedHat Enterprise Linux 4 Update 2 IA32 и x86_64 architectures.
    • Red Hat Enterprise Linux Server release 5.4 (Tikanga) x86_64 architecture.
    • SuSE Linux Enterprise Server 10.0 IA32, IA64, PPC32, PPC64, s390, s390x architectures.
    • SuSE Linux Enterprise Server 11.0 IA32, x86_64 architectures.
    • Ubuntu 9.04 IA32 architecture.
    • Ubuntu 9.10 IA32 architecture.
    • Fedora release 8 (Werewolf) IA32 architecture.
    • Fedora release 10 (Cambridge) x86_64 architecture.
    • Fedora release 12 (Constantine) IA32 architecture.

    For building and running test set extra requirements for software, that are described in "Building test set" and "Running tests" sections, must be fulfilled.

  2. Building test set

    Successful OLVER Core building requires the following components:
    1. LSB 3.1 Software Development Kit (SDK). It can be downloaded at
    2. GNU C/C++ Compiler 3.3.5 or higher
    3. Java Runtime Environment ver. 5 or higher (IBM or Sun preferred); path to java executable should be in PATH variable.
    4. autoconf
    5. automake
    6. libtool
    7. ncurses-devel

    Strictly before building the script must be run to prepare test set. You will be proposed to choose the architecture of system under test and user login used to run tests.


    Launching builing process must be started as the user chosen before.


    Administrator privileges are required for the correct functionality testing of ncurses and subsystem for working with processes.In case current user doesn`t have required privileges, password will be demanded.

    After finishing compilation install of test data is required.


    Building takes about 25 min on Athlon XP 2700+.

    You can delete unuseful files by running the script:


  3. Running tests

    Required components for running tests are

      1. LSB runtime loader: /lib/ If not present, you need to install LSB 3.1 Software Development Kit (SDK). It can be downloaded at

      2. Perl interpreter.

    There are 2 types of test results report generation.
    The first assumes having

      3a. Java Runtime Environment ver. 5 or higher (IBM or Sun preferred); path to java executable must be in PATH variable.

    and is preferred. The second uses only perl interpreter.

    Attention! Built in the test set perl modules are extremely slow,
    so it is strongly recommended to install one of modules based on XML::SAX

       3b. Perl-module, having XML::SAX interface

    Tests are launched using from bin directory

      ./bin/olver_run_tests [ testplan [ timeout ] ]

      testplan is a list of test scenarios to be launched.
      There is an opportunity to exclude unused scenarios

        #str_scenario (not executed)
        integer_scenario (executed)

      By default is used ./bin/testplan

      timeout represents max time of scenario passing in sec.
      After expiring the next element from testplan is processed.
      By default it is 30 min.

    The directory where test traces and generated reports are saves can be set with export:

      export OLVER_REPORT_DIR=...

    By default: /var/opt/lsb/test/olver-core/<timestamp>

  4. Test report generation

    Test report can be generated independently of test running using script


    It is necessary to set the directory with test traces as an environment parameter

      export REPORT_DIR=...

    Otherwise will be used the last directory in

    Reports will be saved in the directory with traces.

    Also you can set the name of parcer to be used

      export OLVER_XML_PARSER=

  5. Browsing test results

    Test results are formed in directory


    You can use any web browser you like to see following reports:

    Test Execution Summary Reports:
      1. In OLVER format: /var/opt/lsb/test/olver-core//summary.htm
      2. In TET format: /var/opt/lsb/test/olver-core//nice_tet.log

    Test Execution Report:

    Requirements Coverage Report:

    For detailed information about test reports see

  6. Troubleshooting

    1. SuSE. Fail to build the agent. Add symbolic links:
        a) libz
            cd /lib
            ln -s
        b) libpam
            cd /lib
            ln -s
        c) libncurses
            cd /lib
            ln -s
    2. SuSE. Can not build olverterm because can not find
       tic (terminfo compiler). Install ncurses-devel package.
    3. Mandriva. Fail to build the agent. Add symbolic links:
        a) libpam
            cd /lib
            ln -s
    4. If you experience problems with building model of the test suite
       make sure that your java environment is Sun or IBM Java Runtime Environment
        version 5 or later. Sun Java is preffered.
    5. On some systems problem may occure with agent build - clog10() function is
       incorrectly defined as
            extern double complex clog10(void);
       in LSB headers on these systems. This is LSB 3.1 Software Development Kit (SDK)
       problem. Correct in /opt/lsb/include/complex.h the above definition to
            extern double complex clog10(double complex)