Closed janivanhala closed 1 week ago
Database related unit testing seems to require to "mock up" extra code somewhere. Swapping to do integration tests as they are half done.
deletion tests need to test if they also delete results and used_blueprints
By latest emails, in these "small" projects, combining unit and integration tests seems to be ok.
"Found" meaning a positive test "NotFound" meaning a negative test "NodeNotFound" meaning the underlying node is not found (negative test) "Relationship" tests from (a) -[to]-> (b) "Advanced" has more individual documentation
Tests:
Test public functions