Changes between Version 2 and Version 3 of FATE/AddingATest

Timestamp:

Apr 12, 2014, 8:12:59 PM (12 years ago)

Author:

Timothy Gu

Comment:

wip

FATE/AddingATest

@@ -19 +19 @@
 ==== 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.
+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 contains tests for audio codecs, and scroll down to a test named `fate-dts`. For convenience, you can also see a copy of the recipe below.
+
+{{{
+FATE_SAMPLES_AUDIO-$(call DEMDEC, MPEGTS, DCA) += fate-dts
+fate-dts: CMD = pcm -i $(TARGET_SAMPLES)/dts/dts.ts
+fate-dts: CMP = oneoff
+fate-dts: REF = $(SAMPLES)/dts/dts.pcm
+}}}
+
+This is one of the simplest tests for FFmpeg. Look at the first quoted line. It adds `fate-dts` to a weird variable containing a call to `DEMDEC`. That function returns
 
 == Filter Tests ==