LUMIERA.clone/tests/46fixture.tests

TESTING "Component Test Suite: Fixture" ./test-suite --group=fixture


PLANNED "detecting Fixture changes" FixtureChangeDetector_test <<END
return: 0
END


TEST "A Segment in the Fixture" FixtureSegment_test <<END
return: 0
END


TEST "ModelPort registry" ModelPortRegistry_test <<END
return: 0
END


TEST "Fixture Node-Graph connection" NodeGraphAttachment_test <<END
return: 0
END


PLANNED "Segmentation integration test" SegmentationIntegration_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: Fixture" ./test-suite --group=fixture`


			`PLANNED "detecting Fixture changes" FixtureChangeDetector_test <<END`
			`return: 0`
			`END`


Dispatcher-Pipeline: create hook for self-validation ...later to be extended into the render nodes network 2023-06-12 01:07:53 +02:00			`TEST "A Segment in the Fixture" FixtureSegment_test <<END`
Dispatcher-Pipeline: remould Segment for on-demand JobTicket generation Use another unit-test (FixtureSegment_test) to guide and cover the transition from the existing fake-implementation to the actual implementation, where the JobTicket will be generated on-demand, from a NodeGraphAttachment 2023-06-08 03:21:43 +02:00			`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			`TEST "ModelPort registry" ModelPortRegistry_test <<END`
			`return: 0`
			`END`


Dispatcher-Pipeline: implement Generation of fake-ExitNodes ...similar to the Generation of complete JobTickets in the initial implementation 2023-06-07 17:21:31 +02:00			`TEST "Fixture Node-Graph connection" NodeGraphAttachment_test <<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			`return: 0`
			`END`


Dispatcher-Pipeline: remould Segment for on-demand JobTicket generation Use another unit-test (FixtureSegment_test) to guide and cover the transition from the existing fake-implementation to the actual implementation, where the JobTicket will be generated on-demand, from a NodeGraphAttachment 2023-06-08 03:21:43 +02:00			`PLANNED "Segmentation integration test" SegmentationIntegration_test <<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			`return: 0`
			`END`