It turns out that the real (not mocked) implementation of JobTicket creation is already required now for this planned (mock)Dispatcher setup; moreover, this real implementation turns out to be almost identical to the mock implementation written recently -- just nested structure of prerequiste JobTickets need to be changed into a similar structur of ExitNodes -- as an aside: rearrange various tests to be more in-line with the envisioned architecture of playback and engine
67 lines
1.1 KiB
Text
67 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 "Setup for render job planning" JobPlanningSetup_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
TEST "Mock support for render job planning" MockSupport_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
PLANNED "scheduler interface" SchedulerInterface_test <<END
|
|
END
|
|
|
|
|
|
PLANNED "Step timing basics" Timings_test <<END
|
|
END
|