• Home
  • Raw
  • Download

Lines Matching refs:LTP

4 This is a step-by-step tutorial on writing a simple C LTP test, where topics
5 of the LTP and Linux kernel testing will be introduced gradually using a
10 LTP tests can be written in C or Shell script. This tutorial is only for tests
11 written in C using the new LTP test API. Note that while we go into some
29 Git-clone the main LTP repository as described in the +README+ and change
30 directory to the checked-out Git repository. We recommend installing the LTP
63 +testcases/kernel/syscalls+, but you should also +git grep+ the entire LTP
66 One way to find a system call which is not currently tested by the LTP is to
69 Something the LTP excels at is ensuring bug-fixes are back ported to
92 is you are planning to use the LTP for.
141 Starting with the +#include+ statement we copy in the main LTP test library
239 is just the executable name, but some tests also take arguments (the LTP has a
308 The LTP follows the Linux style guidelines where possible. Check what happens
312 3.4 Install the LTP and run the test with runtest
325 The LTP contains a library for dealing with the +syscall+ interface, which is
399 relevant definitions into the LTP. This is somewhat like 'vendoring', although
413 into the LTP library and also implemented by the C library. At that point we
518 it in the current working directory and let the LTP test harness handle where
589 The +setup+ callback uses one of the LTP's +SAFE+ functions to create an empty
592 +cleanup+ callback yet because the LTP test harness will recursively delete
599 By this point you may have begun to explore the LTP library headers or older
777 correctly. Note that the LTP has helper functions for creating devices and
802 the LTP's Git-log readable. It also allows us to write a coherent description
997 header, which I have set to the LTP mailing list.
1008 a valid SMTP server set in +.gitconfig+ and also be signed up to the LTP
1023 It doesn't matter whether you know the canonical way of writing an LTP test in
1043 Hopefully you can now grasp the structure of an LTP test and have some idea of
1044 what is available in the LTP test library. There are a vast number of library
1052 from yours. The LTP has a huge and varied user base, so situations you may
1061 multi-process or multi-threaded testing. The LTP library functions work inside
1069 mailing list although you can also use GitHub. The LTP follows similar rules