Lines Matching +full:test +full:- +full:linux

1 Linux Test Project
4 Linux Test Project is a joint project started by SGI, OSDL and Bull developed
7 reliability, robustness, and stability of Linux.
9 The LTP testsuite contains a collection of tools for testing the Linux kernel
10 and related features. Our goal is to improve the Linux kernel and system
11 libraries by bringing test automation to the testing effort. Interested open
14 Project pages are located at: http://linux-test-project.github.io/
17 https://github.com/linux-test-project/ltp/releases
20 http://lists.linux.it/listinfo/ltp
28 https://github.com/linux-test-project/ltp
45 If you have git, autoconf, automake, m4, pkgconf / pkg-config, libc headers,
46 linux kernel headers and other common development packages installed (see
50 $ git clone https://github.com/linux-test-project/ltp.git
56 Now you can continue either with compiling and running a single test or with
62 Shortcut to running a single test
63 ---------------------------------
64 If you need to execute a single test you actually do not need to compile
89 $ make generate-makefiles
92 $ ./foo_1-1.run-test
96 --------------------------------------
104 * If you have a problem see `doc/mini-howto-building-ltp-from-git.txt`.
105 * If you still have a problem see `INSTALL` and `./configure --help`.
111 * If a test returns `TCONF` due to a missing component, check the `./configure`
117 -------------
119 To run all the test suites
126 Note that many test cases have to be executed as root.
128 To run a particular test suite
131 $ ./runltp -f syscalls
137 $ ./runltp -f syscalls -s madvise
142 $ ./runltp --help
145 Test suites (e.g. syscalls) are defined in the runtest directory. Each file
146 contains a list of test cases in a simple format, see doc/ltp-run-files.txt.
148 Each test case has its own executable or script, these can be executed
158 $ testcases/bin/mesgq\_nstest -m none
161 The vast majority of test cases accept the -h (help) switch
164 $ testcases/bin/ioctl01 -h
180 For more info see `doc/user-guide.txt` or online at
181 https://github.com/linux-test-project/ltp/wiki/User-Guidelines.
184 -------------
186 (online at https://github.com/linux-test-project/ltp/tree/master/testcases/network).
193 * `doc/test-writing-guidelines.txt`
194 * `doc/build-system-guide.txt`
195 * `doc/library-api-writing-guidelines.txt`
197 There is also a step-by-step tutorial:
199 * `doc/c-test-tutorial-simple.txt`
204 * https://github.com/linux-test-project/ltp/wiki/Test-Writing-Guidelines
205 * https://github.com/linux-test-project/ltp/wiki/LTP-Library-API-Writing-Guidelines
206 * https://github.com/linux-test-project/ltp/wiki/Build-System
207 * https://github.com/linux-test-project/ltp/wiki/C-Test-Case-Tutorial
211 It's a good idea to test patches on GitHub Actions before posting to mailing