unittest behaviour
DLearner
bmqazwsx123 at gmail.com
Wed Jan 8 11:37:09 UTC 2025
On Wednesday, 18 December 2024 at 07:43:01 UTC, Jonathan M Davis
wrote:
[...]
> - Jonathan M Davis
Thinking about this a little more:
Suggestion:
Leave the current behaviour as default, but introduce an option
(-r ?) so that
```
unittest -r {
}
```
forces a complete rebuild
(for clarity, if the function under test has updated data files,
etc., it is the programmers responsibility that the unittest
contains a script that resets those files).
The motive for all this is to address the situation where the
function under test is not small, but is the top (or near top) of
a complex system wih lots of state,
and the task is to create a test suite that clearly shows that
multiple situations, involving state, have indeed been tested.
More information about the Digitalmars-d-learn
mailing list