Timeline for All unit tests in one executable, or split them up?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 22, 2022 at 3:20 | comment | added | Lothar | I can't see how this matters to the one executable class if you just can add one or two start parameters on the command line. I wrote my test with control flow in the opposite direction. The setup/teardown functions are calling the scripts not the other way around. | |
| Jun 15, 2012 at 6:27 | vote | accept | Benjamin Kloster | ||
| Jun 15, 2012 at 6:20 | comment | added | tdammers | @JBRWilkinson: Just a 30-line shell script. For most of the languages I use, I do have little libraries around for common testing tasks such as running a function, comparing the result to an expected value, and throwing when they don't match. But any given unit testing framework could easily be integrated into such a "meta system", as long as it can run from the command line and signals success/failure through its exit status. | |
| Jun 14, 2012 at 23:47 | comment | added | JBRWilkinson | @tdammers: any particular testing framework? | |
| Jun 14, 2012 at 17:50 | comment | added | Benjamin Kloster | The language agnostic argument is a very good point, since I plan on implementing python bindings for the library down the road. Thanks! | |
| Jun 14, 2012 at 17:41 | history | answered | tdammers | CC BY-SA 3.0 |