On Friday 04 May 2012, Igor Galić wrote: > ----- Original Message ----- > > > Hi, > > > > there are some parts of httpd where unit tests would allow easier > > testing or more complete test coverage than tests written for the > > perl > > framework. Examples include the ap_pcfg_* functions, the varbuf > > API, the regex plus API, and new interfaces that are not yet > > used by any module. > > > > Therefore, I am thinking about adding unit tests to httpd. For > > maximum > > usefulness, such unit tests should be able to access functions > > that are not exported (including static functions). I could > > think of a few > > > ways to achive this: > [snip] > > > Any comments? > > I know the Subversion project has a very complete unit test suit. > How do they approach this?
I am not sure. It seems they only use the test suite to test exported interfaces, but some of those interfaces are considered private in that the header files are not installed on the target system. Of course it would also be a possibility that we simply mark the functions to be tested as non-static. Personally, I think that is ugly, though.
