Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Stefano Sabatini <stefasab@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Stefano Sabatini <stefasab@gmail.com>
Subject: [FFmpeg-devel] [PATCH 3/3] tests: add README.md file with simple instructions
Date: Sun,  3 Apr 2022 15:59:42 +0200
Message-ID: <20220403135942.303691-1-stefasab@gmail.com> (raw)

---
 tests/README.md | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 48 insertions(+)
 create mode 100644 tests/README.md

diff --git a/tests/README.md b/tests/README.md
new file mode 100644
index 0000000000..4bcae0b403
--- /dev/null
+++ b/tests/README.md
@@ -0,0 +1,48 @@
+FFmpeg tests
+============
+
+Tests are useful to make sure that code changes do not introduce regressions.
+
+## FATE tests
+
+FATE (FFmpeg Automated Test Environment) is the system used to test
+regressions and should be used for new changes which affect the API or
+components behavior.
+
+To run all tests, run the following command from the commandline:
+```
+make fate
+```
+
+To get the complete list of tests:
+```
+make fate-list
+```
+
+You can specify a subset of tests to run by specifying the
+corresponding element form the list with the `fate-` prefix, e.g.:
+```
+make fate-ffprobe_compact fate-ffprobe_xml
+```
+
+## FATE samples
+
+By default, FFmpeg uses only the standalone tests. To use the
+collected FATE samples, you need download and configure the tests with
+the FATE samples path.
+
+To upload or update the samples, run the command:
+```
+make fate-rsync SAMPLES=/path/to/samples
+```
+
+Then you need to setup the path where the samples are located, either
+when configuring with:
+```
+./configure --samples=path/to/fate/samples
+```
+
+or when running the tests with:
+```
+FATE_SAMPLES=path/to/fate/samples make fate
+```
-- 
2.25.1

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

             reply	other threads:[~2022-04-03 16:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-03 13:59 Stefano Sabatini [this message]
2022-04-04  8:30 ` Thilo Borgmann
2022-04-05 21:40   ` Stefano Sabatini
2022-04-06  7:24     ` Thilo Borgmann
2022-04-07 22:36       ` Stefano Sabatini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220403135942.303691-1-stefasab@gmail.com \
    --to=stefasab@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git