This was a lot of intricate technical work, and is now verified in-depth, covering all possible cases. __We can now__ * build Nodes * verify in detail correct connectivity * read Node-IDs and processing specifications * maintain a symbolic spec for the arguments of a Port (and beyond that, we can also **invoke nodes**, which remains to be formally verified)
34 lines
547 B
Text
34 lines
547 B
Text
TESTING "Component Test Suite: Render Engine parts" ./test-suite --group=node
|
|
|
|
|
|
|
|
PLANNED "Proc Node basics" NodeBase_test <<END
|
|
END
|
|
|
|
|
|
TEST "Proc Node creation" NodeBuilder_test <<END
|
|
END
|
|
|
|
|
|
TEST "Proc Node test setup" NodeDevel_test <<END
|
|
END
|
|
|
|
|
|
PLANNED "Proc Node data feeds" NodeFeed_test <<END
|
|
END
|
|
|
|
|
|
PLANNED "Proc Node connectivity" NodeLink_test <<END
|
|
END
|
|
|
|
|
|
Test "Proc Node metadata key" NodeMeta_test <<END
|
|
END
|
|
|
|
|
|
PLANNED "Proc Node operation modes" NodeOpera_test <<END
|
|
END
|
|
|
|
|
|
PLANNED "Proc Node engine storage setup" NodeStorage_test <<END
|
|
END
|