fate.txt 1.5 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546
  1. FATE Automated Testing Environment
  2. FATE provides a regression testsuite that can be run locally or configured
  3. to send reports to fate.ffmpeg.org.
  4. In order to run, it needs a large amount of data (samples and references)
  5. that is provided separately from the actual source distribution.
  6. Use the following command to get the fate test samples
  7. # rsync -aL rsync://rsync.mplayerhq.hu:/samples/fate-suite/ fate/fate-suite
  8. # rsync -aL rsync://fate-suite.libav.org:/fate-suite/ fate-suite
  9. To inform the build system about the testsuite location, pass
  10. `--samples=<path to the samples>` to configure or set the SAMPLES Make
  11. variable or the FATE_SAMPLES environment variable to a suitable value.
  12. For information on how to set up FATE to send results to the official FFmpeg
  13. testing framework, please refer to the following wiki page:
  14. http://wiki.multimedia.cx/index.php?title=FATE
  15. FATE Makefile targets:
  16. fate-list
  17. Will list all fate/regression test targets.
  18. fate
  19. Run the FATE test suite (requires the fate-suite dataset).
  20. Fate Makefile variables:
  21. V
  22. Verbosity level, can be set to 0, 1 or 2.
  23. * 0: show just the test arguments
  24. * 1: show just the command used in the test
  25. * 2: show everything
  26. SAMPLES
  27. Specify or override the path to the FATE samples at make time, it has a
  28. meaning only while running the regression tests.
  29. THREADS
  30. Specify how many threads to use while running regression tests, it is
  31. quite useful to detect thread-related regressions.
  32. Example:
  33. make V=1 SAMPLES=/var/fate/samples THREADS=2 fate