...continue to proceed test-driven ...scheduler internals turn out to be intricate and cohesive, and thus the only hope is to adhere to strict testing discipline
37 lines
550 B
Text
37 lines
550 B
Text
TESTING "Component Test Suite: Scheduler" ./test-suite --group=engine
|
|
|
|
|
|
|
|
PLANNED "Activity observation framework" ActivityDetector_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
PLANNED "BlockFlow memory management scheme" BlockFlow_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
PLANNED "Scheduler Activity Language" SchedulerActivity_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
PLANNED "Scheduler Layer-1" SchedulerInvocation_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
PLANNED "Scheduler Layer-2" SchedulerCommutator_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
|
|
PLANNED "Scheduler Integration" SchedulerUsage_test <<END
|
|
return: 0
|
|
END
|