Changes between Version 1 and Version 2 of FATE/AddingATest

Timestamp:

Apr 12, 2014, 8:08:58 PM (12 years ago)

Author:

Timothy Gu

Comment:

WIP

FATE/AddingATest

@@ -1 +1 @@
 = Adding a FATE Test =
 
-There are two main kinds of FATE test: using existing samples (primarily useful with decoder testing), and generating an artificial sample for testing.
+There are two main kinds of FATE test: using existing samples (primarily useful with decoder testing), and using an artificially generated sample for testing.
 
-== Encoder, and Filter Tests ==
+The recipes for the tests written in GNU Make are located under `tests/fate` in the FFmpeg source. Because FFmpeg has a very complex codebase, differing code needs a wide variety of tests. Let us start with the common part of the tests.
+
+== Four Parts of a Test ==
+
+A typical test usually consists of four parts:
+
+1. Registration: meaning that `make fate` automatically execute the test you want to add;
+2. Dependencies: which are usually samples for a format, a generated sample, or a program specifically written to test this feature;
+3. Configuration: this part is the most important of all, because it controls how the test will be run.
+
+Let us focus on the separate parts of a test.
+
+=== Registration ===
+
+==== One Test for one Feature ====
+
+The most common case is that only one test is allocated for one feature (e.g. decoder, muxer, hashing algorithm, etc.). Let's open `tests/fate/audio.mak`, which is a file containing tests for audio codecs.
+
+== Filter Tests ==
+
+
 
 == Decoder Tests ==
@@ -10 +30 @@
 
 == libswresample Tests ==
-
-==