lumiera_/tests/45builder.tests

TESTING "Component Test Suite: Builder" ./test-suite --group=builder


TEST "BuilderTool_test" BuilderTool_test <<END
out: apply \(tool, clip\);
out: Clip on media : Asset\(VIDEO:lumi.test-1 v1\)
out: apply \(tool, test1\);
out: treat \(AbstractMO&\);
out: apply \(tool, test2\);
out: catch-all-function called...
return: 0
END


PLANNED "BuildSegment_test" BuildSegment_test <<END
END
re-arrange tests according to layer structure the buildsystem will now pick up and link all test cases according to the layer, e.g. backend tests will automatically be linked against the backend + library solely. 2013-01-07 05:43:01 +01:00			`TESTING "Component Test Suite: Builder" ./test-suite --group=builder`
TDBS (test driven brain storming) :-) 2007-09-03 02:33:47 +02:00

covered the more esoteric cases for visiting tools and made BuilderTool work 2007-11-29 07:07:14 +01:00			`TEST "BuilderTool_test" BuilderTool_test <<END`
test: Finished regexing the last tests 2009-02-12 11:49:11 +01:00			`out: apply \(tool, clip\);`
			`out: Clip on media : Asset\(VIDEO:lumi.test-1 v1\)`
			`out: apply \(tool, test1\);`
			`out: treat \(AbstractMO&\);`
			`out: apply \(tool, test2\);`
Refactorings regarding use of smart-ptr, Placement and BuilderTool 2008-05-19 08:46:19 +02:00			`out: catch-all-function called...`
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`
WIP generalizing my builder tools to use the acyclic visitor. inspired by Loki; ichthyo intends to use this pattern for typesafe visiting within the EDL too... 2007-11-27 06:40:51 +01:00			`END`


TDBS (test driven brain storming) :-) 2007-09-03 02:33:47 +02:00			`PLANNED "BuildSegment_test" BuildSegment_test <<END`
			`END`