LUMIERA.clone/tests/11time.tests

TESTING "Time conversion" ./test-time

TEST "basic functionality" basic <<END
err: ECHO: .*: 0:00:00.000
err: ECHO: .*: 3:55:20.700
return: 0
END

TEST "frame rate dependent calculations" fps <<END
return: 0
END

TEST "ntsc drop-frame calculations" ntsc_drop_frame << END
return: 0
END
Add unit tests for time.c 2010-12-06 16:19:17 +01:00			`TESTING "Time conversion" ./test-time`

			`TEST "basic functionality" basic <<END`
correct expected values for timehandling tests regarding frames: we don't round, we truncate towards the next lower integer 2011-02-13 23:12:36 +01:00			`err: ECHO: .*: 0:00:00.000`
			`err: ECHO: .*: 3:55:20.700`
test-suite: fix lots of missing return value checks without that check, in theory our test runner will tolerate a non-zero return value, like throwing or failing an assert, which is not what we want.... guess these happenend to get in by forgetting to add this check when switching a test from PLANNED to TEST 2016-01-28 22:30:24 +01:00			`return: 0`
Add unit tests for time.c 2010-12-06 16:19:17 +01:00			`END`
Improved frame counting capabilities for time lib. Unit tests. 2010-12-13 18:16:15 +01:00
			`TEST "frame rate dependent calculations" fps <<END`
test-suite: fix lots of missing return value checks without that check, in theory our test runner will tolerate a non-zero return value, like throwing or failing an assert, which is not what we want.... guess these happenend to get in by forgetting to add this check when switching a test from PLANNED to TEST 2016-01-28 22:30:24 +01:00			`return: 0`
Improved frame counting capabilities for time lib. Unit tests. 2010-12-13 18:16:15 +01:00			`END`
Add support for NTSC drop-frame timecode. 2010-12-13 18:22:12 +01:00
			`TEST "ntsc drop-frame calculations" ntsc_drop_frame << END`
test-suite: fix lots of missing return value checks without that check, in theory our test runner will tolerate a non-zero return value, like throwing or failing an assert, which is not what we want.... guess these happenend to get in by forgetting to add this check when switching a test from PLANNED to TEST 2016-01-28 22:30:24 +01:00			`return: 0`
Add support for NTSC drop-frame timecode. 2010-12-13 18:22:12 +01:00			`END`