unitizer
unitizer copied to clipboard
brodieG
Easy R Unit Tests
It is a bit disorienting when a test is accepted/rejected and the next test comes along with a lot of screen output. We need some visual cue to let us...
Right now we use ENTER at an empty prompt to re-prompt, which is a pretty wasteful use of the simplest key stroke. Particularly in `review` mode, it would be nice...
Currently we're resetting state without checking whether the state should be from a reference or a new object. This is an issue with deleted items for which clearly the state...
For example, not sure it should come up in this instance where we just put an arbitrary expression at the prompt: ``` > validate(INT.1 || NULL || LGL, "hello", format...
In particular, stuff like: ``` Warning: stack imbalance in '.Call', 178 then 177 Warning: stack imbalance in 'withVisible', 170 then 169 Warning: stack imbalance in '
Related to #197, it would be good to confirm that all the values in `[email protected][[i]]@glob.indices` actually map to a value in `[email protected]` when unitizers are stored and loaded. There is...
May need to consider moving away from S4 test items; really too slow.
Got: ``` | Unable to compare value: comparison function `` returned something | other than TRUE, FALSE, or character vector (NULL of length 0) ``` When using: ``` unitizer_sect("stdout", compare=unitizer:::comp_stdout,...
Hopefully this allows us to get around some of the ungraceful exits we're subject to currently. From NEWS: > In most cases user interrupt handlers will be called with a...
If a user provides a custom comparison function, they may well not want the diff shown.