Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • The language agnostic argument is a very good point, since I plan on implementing python bindings for the library down the road. Thanks! Commented Jun 14, 2012 at 17:50
  • @tdammers: any particular testing framework? Commented Jun 14, 2012 at 23:47
  • @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. Commented Jun 15, 2012 at 6:20
  • 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. Commented Jan 22, 2022 at 3:20