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.
In case of compiled package it is /opt/lsb/test/olver-core.
Content
- Requirements for software and hardware
- Building test set
- Running tests
- Generating test report
- Browsing test results
- Possible troubles with building
- 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.
- Building test set
Successful OLVER Core building requires the following components:- LSB 3.1 Software Development Kit (SDK). It can be downloaded at http://www.linux-foundation.org/en/Downloads
- GNU C/C++ Compiler 3.3.5 or higher
- Java Runtime Environment ver. 5 or higher (IBM or Sun preferred); path to java executable should be in PATH variable.
- autoconf
- automake
- libtool
- ncurses-devel
- Running tests
Required components for running tests are 1. LSB runtime loader: /lib/ld-lsb.so.3. If not present, you need to install LSB 3.1 Software Development Kit (SDK). It can be downloaded at http://www.linux-foundation.org/en/Downloads 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> - Test report generation
Test report can be generated independently of test running using script ./bin/olver_report 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
/var/opt/lsb/test/olver-core Reports will be saved in the directory with traces. Also you can set the name of parcer to be used export OLVER_XML_PARSER= - Browsing test results
Test results are formed in directory /var/opt/lsb/test/olver-core/<timestamp> 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:
/var/opt/lsb/test/olver-core//report/index.html Requirements Coverage Report:
/var/opt/lsb/test/olver-core//result.htm. For detailed information about test reports see http://linuxtesting.org/downloads/olver-reports.pdf - Troubleshooting
1. SuSE. Fail to build the agent. Add symbolic links:
a) libz
su
cd /lib
ln -s libz.so.1 libz.so
b) libpam
su
cd /lib
ln -s libpam.so.0 libpam.so
c) libncurses
su
cd /lib
ln -s libncurses.so.5 libncurses.so
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
su
cd /lib
ln -s libpam.so.0 libpam.so
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)
»