Ichthyostega
f2cbac14e2
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
37 lines
701 B
Text
37 lines
701 B
Text
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
|
|
|
|
|
|
PLANNED "detecting Fixture changes" FixtureChangeDetector_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
TEST "ModelPort registry" ModelPortRegistry_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
TEST "Output pipe mapping" OutputMapping_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
PLANNED "Segmentation datastructure" SegmentationDatastructure_test <<END
|
|
return: 0
|
|
END
|
|
|