Rejig the test suite
glenjamin opened this issue · comments
While implemented #9 I realise the test suite is too granular - lots of features are tested against lots of different API methods.
This has worked quite well up til now - but the combinatorial explosion of functionality through the flexible API is making it quite tricky.
I reckon the implementation should be split into 3 rough layers, and only have some light-ish integration tests between the three.
- Tree traversal
- Creating node-finder functions
- Public API