Linux Test Project

Linux Test Project is sponsored by SGI, OSDL, and Bull joint project of IBM, Cisco, Fujitsu, SUSE, Red Hat, Oracle and other development and maintenance. The project's objective is to provide a test to the open source community to validate the reliability, robustness and stability of Linux.

LTP test suite contains a collection of test Linux kernel and related features of the tool. Our goal is to improve the Linux kernel and system libraries by the introduction of test automation testing. Interested open source contributors are encouraged to join.

Project page located at:http : //linux-test-project.github.io/

The latest images are always available at the following locations:https : //github.com/linux-test-project/ltp/releases

Discussion on the item occurs in ltp mailing list:http : //lists.linux.it/listinfo/ltp

git repository located on GitHub:https : //github.com/linux-test-project/ltp

Patch example in:https : //patchwork.ozlabs.org/project/ltp/list/

warn!

These tests have to be careful!

Do not run them on a production system. Growth files, doio and iogen special emphasis on the system I / O functions, although they should not cause problems in the normal operation of the system, but they are designed to discover (or causing) a problem.

Quick Guide to run tests

If you install git, autoconf, automake, m4, pkgconf / pkg-config, libc header files, linux kernel headers and other common development package (See INSTALL and travis / * .sh), the following may occur Condition:

$ git clone https://github.com/linux-test-project/ltp.git
$ cd ltp
$ make autotools
$ ./configure

Now, you can continue to compile and run a single test, can continue to build and install the entire test suite.

For the optional library dependencies, seetravis/The main release directory script. You can also use./build.shScript to build the entire LTP.

Shortcut to run a single test

If you need to perform a test, you do not need to actually compile the entire LTP, if you want to run syscall test case, you should be able to perform the following tasks.

$ cd testcases/kernel/syscalls/foo
$ make
$ PATH=$PATH:$PWD ./foo01

Shell test case is more complicated, because they require a point to Shell library and the path to a compiled binary program help, but under normal circumstances, should be used.

$ cd testcases/lib
$ make
$ cd ../commands/foo
$ PATH=$PATH:$PWD:$PWD/../../lib/ ./foo01.sh

Open Posix Testsuite has its own build system, you need to generate a Makefile, and then compilation should be carried out in a subdirectory.

$ cd testcases/open_posix_testsuite/
$ make generate-makefiles
$ cd conformance/interfaces/foo
$ make
$ ./foo_1-1.run-test

Compile and install all the test cases

$ make
$ make install

This will install the LTP/opt/ltp。

• If you have questions, please seedoc/mini-howto-building-ltp-from-git.txt。
• If the problem persists, seeINSTALLwith./configure --help。
• If that fails, ask for help on the mailing list or Github.

If you can not find its configuration script build dependencies, some tests will be disabled.

• ifTCONFDue to lack of components caused by the test return, please check./configureOutput.
• If due to lack of user or group and the test fails, refer to the "Quick Start" sectionINSTALL。

Run test

Run all test suites

$ cd /opt/ltp
$ ./runltp

Please note that many test cases to be executed as root.

Run a specific test suite

$ ./runltp -f syscalls

To run all the tests andmadviseThe name

$ ./runltp -f syscalls -s madvise

See also

$ ./runltp --help

Test suites (such as syscalls) defined in runtest directory. Each file contains a list of test cases simple format, see doc / ltp-run-files.txt.

Each test has its own executable files or scripts, can be executed directly

$ testcases/bin/abort01

Some people argue

$ testcases/bin/fork13 -i 37

The vast majority of test cases accepted -h (help) switch

$ testcases/bin/ioctl01 -h

Many of the requirements set certain environment variables

$ LTPROOT=/opt/ltp PATH="$PATH:$LTPROOT/testcases/bin" testcases/bin/wc01.sh

The most common is the need to set the path variable, you need to setLTPROOTBut there are many other variables,runltpUsually set these variables for you.

Please note that all shell scripts needPATHset up. However, this is not limited to shell scripts, many C-based tests also need an environment variable.

For more information, seehttps://github.com/linux-test-project/ltp/wiki/User-Guidelinesdoc/user-guide.txtOr available online.

Network test

Network testing requires certain settings, such astestcases/network/README.md (existOn https://github.com/linux-test-project/ltp/tree/master/testcases/networkOnline description) and theINSTALL。