I think you are wasting your time using the idea of visualization for debugging. Instead, you should have a method that checks the entire tree for correctness (and describes the context of errors in great detail).
Then, during testing, call this method after each step that changes the tree structure. Thus, it is relatively easy to identify errors - and probably faster than viewing a visual presentation.
source
share