unitizer
unitizer copied to clipboard
brodieG
Easy R Unit Tests
Would need good references (e.g. `untz015>` at the prompt), and the ability to easily get to browse to that test (e.g. "q" to exit pager, then "B015" or some such...
Typical scenario is: 1. run unitize_dir 2. one of the files has errors, all others pass 3. view errors, fix source, hit R 4. on re-evaluation, success so taken back...
``` # Failed test #1: for non-existent paths, `pretty_path` is expected to return # the input. Internally, it calls `normalizePath(..., mustWork=FALSE)`, which # is likely returning the full path to...
Unfortunately, all our classes are lowerCamelCase, when they should be UpperCamelCase, with only methods in LowerCamelCase. This is going to be a PITA to change so we'll probably never fix,...
Maybe even make it part of the prompt? ``` #043> ```
How do we handle reference objects that are modified by subsequent tests: ``` DT
Technically we can retrieve the stuff out of the `unitizer`s that are returned, but this isn't well documented, etc.
Right now accepting multiple tests leads to three prompts: ``` unitizer> YY 1. res . . . . . . . . . . . . . . . ....
In this cases, we have no changes, only unreviewed, should consider not prompting, particularly if it is a fast evaluation: ``` - New -------------------------------------------------------------------------- | The following test is new....