Refactor for unit testing #34
Labels
k: refactor
reorganization of existing code without function changes
k: repo
the repository's organization overall
p: repo
all crates, or the repo itself
During my first pass at writing tests, I didn't bother refactoring, partly because this GUI system is... kinda complex and I need to refactor it cleaner. Specifically, I need a nicer way to write UI unit tests that doens't depend too much on exact, charcater-by-character looks. Or I need to stabilize the UI enough to confidently write tests asserting exact, character-by-character looks.
cargo-tarpaulin
or similarThe text was updated successfully, but these errors were encountered: