lumiera_documentation/tests/48playout.tests

TESTING "Component Test Suite: Player and Output" ./test-suite --group=play


PLANNED "Dummy Player setup" DummyPlayConnection_test <<END
return: 0
END


TEST "Output connection API" OutputAllocState_test <<END
return: 0
END


TEST "Output Slot Protocol" OutputSlotProtocol_test <<END
return: 0
END


PLANNED "Timing constraints" TimingConstraints_test <<END
return: 0
END
Dispatcher-Pipeline: prepare test for the new NodeGraphAttachment 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 2023-06-07 04:03:00 +02:00			`TESTING "Component Test Suite: Player and Output" ./test-suite --group=play`
Test-driven brainstorming: diagnostic adaptor for the engine 2011-08-16 03:02:55 +02:00


test-driven brainstorming: how to use the dummy playback? this is an idea how to test a test setup :) 2012-01-23 02:25:12 +01:00			`PLANNED "Dummy Player setup" DummyPlayConnection_test <<END`
			`return: 0`
			`END`


BufferProvider: complete the clean-up effort Looking through all my work notes, it seems that all the problematic aspects are now solved in a satisfactory way. * it is clear how to dependency-inject a `BufferProvider` * the internals of the `BufferProvider` front-End have been restructured * there are now two ''pillars'' of the implementation: `BufferStage` and `BufferStore` * both can be subclassed independently * `BufferProviderSetup` exposes a proxying-mechanism (used for `DiagnosticBufferProvider`) * the `BufferMetadata` have been reviewed and some minor details were rectified * after a re-Design of `OutputSlot`, `BuffHandle` can now be used as unified front-End * both `DiagnosticBufferProvider` and `DiagnosticOutputSlot` have been rewritten * they are now independent, self-contained specialisations, layered on top Overall, what might seem like a detour, was an important step towards well-balanced structures and a better understanding of the Render Engine. 2026-04-13 23:13:55 +02:00			`TEST "Output connection API" OutputAllocState_test <<END`
			`return: 0`
			`END`


OutputSlot : simulated usage protocol passes unit test OutputSlotProtocol_test Some parts are still missing - timings _ initialisation 2012-01-08 03:06:32 +01:00			`TEST "Output Slot Protocol" OutputSlotProtocol_test <<END`
Test-driven brainstorming: diagnostic adaptor for the engine 2011-08-16 03:02:55 +02:00			`return: 0`
			`END`
some musing about timing constraints and quantisation 2012-02-05 00:25:22 +01:00

			`PLANNED "Timing constraints" TimingConstraints_test <<END`
			`return: 0`
			`END`