1 \input texinfo @c -*- texinfo -*-
3 @settitle FATE Automated Testing Environment
5 @center @titlefont{FATE Automated Testing Environment}
14 FATE provides a regression testsuite embedded within the Libav build system.
15 It can be run locally and optionally configured to send reports to a web
16 aggregator and viewer @url{http://fate.libav.org}.
18 It is advised to run FATE before submitting patches to the current codebase
19 and provide new tests when submitting patches to add additional features.
23 @section Samples and References
24 In order to run, FATE needs a large amount of data (samples and references)
25 that is provided separately from the actual source distribution.
27 To inform the build system about the testsuite location, pass
28 @option{--samples=<path to the samples>} to @command{configure} or set the
29 @var{SAMPLES} Make variable or the @var{LIBAV_SAMPLES} environment variable
32 To use a custom wrapper to run the test, pass @option{--target-exec} to
33 @command{configure} or set the @var{TARGET_EXEC} Make variable.
35 The dataset is available through @command{rsync}, is possible to fetch
36 the current sample using the straight rsync command or through a specific
37 @ref{Makefile target}.
40 # rsync -aL rsync://fate-suite.libav.org/fate-suite/ fate-suite
44 # make fate-rsync SAMPLES=fate-suite
49 FATE regression test can be run through @command{make}.
50 Specific Makefile targets and Makefile variables are available:
52 @anchor{Makefile target}
53 @section FATE Makefile targets
57 List all fate/regression test targets.
60 Shortcut to download the fate test samples to the specified testsuite location.
63 Run the FATE test suite (requires the fate-suite dataset).
66 @section FATE Makefile variables
69 Verbosity level, can be set to 0, 1 or 2.
73 show just the test arguments
76 show just the command used in the test
83 Specify or override the path to the FATE samples at make time, it has a
84 meaning only while running the regression tests.
87 Specify how many threads to use while running regression tests, it is
88 quite useful to detect thread-related regressions.
91 Specify which threading strategy test, either @var{slice} or @var{frame},
92 by default @var{slice+frame}
95 Specify a mask to be applied to autodetected CPU flags.
98 Specify or override the wrapper used to run the tests.
101 Set to @var{1} to generate the missing or mismatched references.
105 make V=1 SAMPLES=/var/fate/samples THREADS=2 CPUFLAGS=mmx fate
108 @chapter Automated Tests
109 In order to automatically testing specific configurations, e.g. multiple
110 compilers, @command{tests/fate.sh} is provided.
112 This shell script builds Libav, runs the regression tests and prepares
113 a report that can be sent to @url{http://fate.libav.org/} or directly
116 @section Testing Profiles
117 The configuration file passed to @command{fate.sh} is shell scripts as well.
119 It must provide at least a @var{slot} identifier, the @var{repo} from
120 which fetch the sources, the @var{samples} directory, a @var{workdir} with
121 enough space to build and run all the tests.
122 Optional submit command @var{fate_recv} and a @var{comment} to describe
123 the testing profile are available.
125 Additional optional parameter to tune the Libav building and reporting process
129 slot= # some unique identifier
130 repo=git://git.libav.org/libav.git # the source repository
131 #branch=release/10 # the branch to test
132 samples=/path/to/fate/samples
133 workdir= # directory in which to do all the work
134 fate_recv="ssh -T fate@@fate.libav.org" # command to submit report
135 comment= # optional description
136 build_only= # set to "yes" for a compile-only instance that skips tests
138 # the following are optional and map to configure options
153 extra_conf= # extra configure options not covered above
155 #make= # name of GNU make if not 'make'
156 makeopts= # extra options passed to 'make'
157 #tar= # command to create a tar archive from its arguments on
158 # stdout, defaults to 'tar c'
161 @section Special Instances
162 The @var{TARGET_EXEC} option provides a way to run FATE wrapped in
163 @command{valgrind}, @command{qemu-user} or @command{wine} or on remote targets
164 through @command{ssh}.
166 @section Submitting Reports
167 In order to send reports you need to create an @command{ssh} key and send it
168 to @email{root@@libav.org}.