Skip to content
C Shell HTML Makefile Python C++ Other
Branch: master
Clone or download
Pull request Compare This branch is 1 commit ahead, 4 commits behind linux-test-project:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
doc capability: Introduce capability API Sep 11, 2019
include capability: library tests Sep 11, 2019
lib lib: Fix safe_mount() when mounting NTFS as r/w on kernels with NTFS Sep 17, 2019
libs uevent03: Use a generic way to get sysname Sep 11, 2019
m4 m4: clean up ltp-signalfd.m4 Aug 2, 2019
pan ltp-pan: Increase allowed width of test name in logs Aug 2, 2018
runtest BPF: Sanity check creating a program Sep 10, 2019
scenario_groups kernel/uevent: Add uevent01 Sep 2, 2019
scripts
testcases syscalls/madvise09: Workaround failures on newer kernels Sep 13, 2019
testscripts sh: Replace GPL verbose text by SPDX license identifier Jun 19, 2019
tools net: Disable building tst_get_unused_port in old API May 24, 2019
travis
utils utils/ffsb: Add missing fhstat() signature + includes Aug 9, 2019
.gitignore add confXXXXX-directories to gitignore Sep 26, 2018
.gitmodules gitmodules: update mce-test repo URL May 31, 2012
.travis.yml travis: Reorder builds to speedup testing Mar 26, 2019
COPYING update GPLv2 text in COPYING Jan 26, 2015
IDcheck.sh Update FSF address Oct 19, 2012
INSTALL
Makefile Makefile: Fix target redefinition Apr 30, 2019
Makefile.release Use `tar [..] .' instead of `tar [..] *'. Dec 14, 2010
README.kernel_config p9auth: remove this test Sep 17, 2014
README.md README: Add note about testing with Travis CI Jun 6, 2019
TODO Update TODO Feb 17, 2016
VERSION LTP 20190517 May 17, 2019
build.sh build: Move -Werror-implicit-function-declaration from make to build.sh Aug 9, 2019
configure.ac
execltp.in
ltpmenu shell: fix bashisms: s/&>/>$1 2>&1/ Dec 1, 2016
runltp runltp: Remove unused -n option Apr 15, 2019
ver_linux ver_linux: Fix util-linux version for some distros Jun 7, 2019

README.md

Linux Test Project

Linux Test Project is a joint project started by SGI, OSDL and Bull developed and maintained by IBM, Cisco, Fujitsu, SUSE, Red Hat, Oracle and others. The project goal is to deliver tests to the open source community that validate the reliability, robustness, and stability of Linux.

The LTP testsuite contains a collection of tools for testing the Linux kernel and related features. Our goal is to improve the Linux kernel and system libraries by bringing test automation to the testing effort. Interested open source contributors are encouraged to join.

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

The latest image is always available at: https://github.com/linux-test-project/ltp/releases

The discussion about the project happens at ltp mailing list: http://lists.linux.it/listinfo/ltp

The git repository is located at GitHub at: https://github.com/linux-test-project/ltp

The patchwork instance is at: https://patchwork.ozlabs.org/project/ltp/list/

Warning!

Be careful with these tests!

Don't run them on production systems. Growfiles, doio, and iogen in particular stress the I/O capabilities of systems and while they should not cause problems on properly functioning systems, they are intended to find (or cause) problems.

Quick guide to running the tests

If you have git, autoconf, automake, m4, the linux headers and the common developer packages installed, the chances are the following will work.

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

Now you can continue either with compiling and running a single test or with compiling and installing the whole testsuite.

Shortcut to running a single test

If you need to execute a single test you actually do not need to compile the whole LTP, if you want to run a syscall testcase following should work.

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

Shell testcases are a bit more complicated since these need a path to a shell library as well as to compiled binary helpers, but generally following should work.

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

Open Posix Testsuite has it's own build system which needs Makefiles to be generated first, then compilation should work in subdirectories as well.

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

Compiling and installing all testcases

$ make
$ make install

This will install LTP to /opt/ltp.

  • If you have a problem see doc/mini-howto-building-ltp-from-git.txt.
  • If you still have a problem see INSTALL and ./configure --help.
  • Failing that, ask for help on the mailing list or Github.

Some tests will be disabled if the configure script can not find their build dependencies.

  • If a test returns TCONF due to a missing component, check the ./configure output.
  • If a tests fails due to a missing user or group, see the Quick Start section of INSTALL.

To run all the test suites

$ cd /opt/ltp
$ ./runltp

Note that many test cases have to be executed as root.

To run a particular test suite

$ ./runltp -f syscalls

To run all tests with madvise in the name

$ ./runltp -f syscalls -s madvise

Also see

$ ./runltp --help

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

Each test case has its own executable or script, these can be executed directly

$ testcases/bin/abort01

Some have arguments

$ testcases/bin/fork13 -i 37

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

$ testcases/bin/ioctl01 -h

Many require certain environment variables to be set

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

Most commonly, the path variable needs to be set and also LTPROOT, but there are a number of other variables, runltp usually sets these for you.

Note that all shell scripts need the PATH to be set. However this is not limited to shell scripts, many C based tests need environment variables as well.

Developers corner

Before you start you should read following documents:

  • doc/test-writing-guidelines.txt
  • doc/build-system-guide.txt

There is also a step-by-step tutorial:

  • doc/c-test-tutorial-simple.txt

If something is not covered there don't hesitate to ask on the LTP mailing list. Also note that these documents are available online at:

Although we accept GitHub pull requests, the preferred way is sending patches to our mailing list.

It's a good idea to test patches on Travis CI before posting to mailing list. Our travis setup covers various architectures and distributions in order to make sure LTP compiles cleanly on most common configurations. For testing you need to sign up to Travis CI, enable running builds on your LTP fork on https://travis-ci.org/account/repositories and push your branch.

You can’t perform that action at this time.