Changes between Version 1 and Version 2 of FATE/AddingATest


Ignore:
Timestamp:
Apr 12, 2014, 11:08:58 PM (6 years ago)
Author:
Timothy_Gu
Comment:

WIP

Legend:

Unmodified
Added
Removed
Modified
  • FATE/AddingATest

    v1 v2  
    11= Adding a FATE Test =
    22
    3 There are two main kinds of FATE test: using existing samples (primarily useful with decoder testing), and generating an artificial sample for testing.
     3There are two main kinds of FATE test: using existing samples (primarily useful with decoder testing), and using an artificially generated sample for testing.
    44
    5 == Encoder, and Filter Tests ==
     5The 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.
     6
     7== Four Parts of a Test ==
     8
     9A typical test usually consists of four parts:
     10
     111. Registration: meaning that `make fate` automatically execute the test you want to add;
     122. Dependencies: which are usually samples for a format, a generated sample, or a program specifically written to test this feature;
     133. Configuration: this part is the most important of all, because it controls how the test will be run.
     14
     15Let us focus on the separate parts of a test.
     16
     17=== Registration ===
     18
     19==== One Test for one Feature ====
     20
     21The 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.
     22
     23== Filter Tests ==
     24
     25
    626
    727== Decoder Tests ==
     
    1030
    1131== libswresample Tests ==
    12 
    13 ==