--- opus <[EMAIL PROTECTED]> wrote:
> help out with ICD testing. I would like to see unit testing as well, > any > thoughts? On the subject of "unit testing". I've started a new system at work. Say I write a file caled foobar.c, I make anoher called "foobar_UT.c" (or a foobarUT shell script if foobar.c contains a "main()" and then in the automake input file I have a binary target called foobar.UT and I put this target in "TESTS". so may "make check" target will run all the "UT" or"Unit Test" drivers My project is runnng about 47K lines of code and it's easy to break stuff, Having a full up unit test target makes it easy to run prior to _every_ CVS commit. Yes it's a lot of work to setup but it's mission critical software and I'm paid full time to work on it. I lot of people will put regresion tests in the "make check" target, I have some in there too, along with the *UT" tests. UT is about the only way to test all the code paths as so many of those paths typically handle rare errors and "corner cases". the UT code is also a good exaple that other programmerscan lok at to understand the API under test. The name convention of *UT makes it easy to find the file. For an Open source project like OpenPBX that hopefully will get hacked on by a large number of developers having some kind of built-in test would be a big help. Chris Albertson Home: 310-376-1029 [EMAIL PROTECTED] Cell: 310-990-7550 Office: 310-336-5189 [EMAIL PROTECTED] KG6OMK __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Openpbx-dev mailing list [email protected] http://lists.openpbx.org/mailman/listinfo/openpbx-dev
