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
69 lines
1.1 KiB
Text
69 lines
1.1 KiB
Text
TESTING "Component Test Suite: Render Engine parts" ./test-suite --group=engine
|
|
|
|
|
|
|
|
TEST "Test support: dummy frames" TestFrame_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
TEST "Test support: dummy buffer provider" TrackingHeapBlockProvider_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
TEST "Buffer provider diagnostics" BufferProviderProtocol_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
TEST "buffer metadata type keys" BufferMetadataKey_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
TEST "buffer metadata and state transitions" BufferMetadata_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
PLANNED "buffer table" BuffTable_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
PLANNED "Engine Interface basics" EngineInterface_test <<END
|
|
END
|
|
|
|
|
|
PLANNED "Engine calculation streams" CalcStream_test <<END
|
|
END
|
|
|
|
|
|
PLANNED "Frame Dispatcher Interface" DispatcherInterface_test <<END
|
|
END
|
|
|
|
|
|
TEST "Render job properties" JobHash_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
PLANNED "Proc Node basics" NodeBasic_test <<END
|
|
END
|
|
|
|
|
|
PLANNED "Proc Node fabrication" NodeFabrication_test <<END
|
|
END
|
|
|
|
|
|
PLANNED "Proc Node operation modes" NodeOperation_test <<END
|
|
END
|
|
|
|
|
|
PLANNED "source reading Node" NodeSource_test <<END
|
|
END
|
|
|
|
|
|
PLANNED "scheduler interface" SchedulerInterface_test <<END
|
|
END
|