* the implementation logic of the Scheduler is essentially complete now * all functionality necessary for the worker-function has been demonstrated As next step, the »Scheduler Service« can be assembled from the two Implementation Layers, the Activity-Language and the `BlockFlow` allocator This should then be verified by a multi-threaded integration test...
43 lines
602 B
Text
43 lines
602 B
Text
TESTING "Component Test Suite: Scheduler" ./test-suite --group=engine
|
|
|
|
|
|
|
|
TEST "Activity observation framework" ActivityDetector_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
TEST "BlockFlow memory management scheme" BlockFlow_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
TEST "Scheduler Activity Language" SchedulerActivity_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
TEST "Scheduler Layer-1" SchedulerInvocation_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
TEST "Scheduler Layer-2" SchedulerCommutator_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
PLANNED "Scheduler Integration" SchedulerUsage_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
TEST "Worker Thread Service" WorkForce_test <<END
|
|
return: 0
|
|
END
|