Hello,
this probably needs a more elaborate discussion and planning, being somehow related to unit testing that is planned to be approached for 5.0.
IMO, anything for testing a module should be in a subfolder inside the module directory or inside a directory dedicated for testing. It won't be that nice to have them at the same level with module directories, will be a lot of noise there as a module may have more than one unit test.
Cheers,
Daniel
Hi! In order to be able to test the API for the http_client I have created a separate module. I couldn’t let it live in the same directory, so I created a new module directory for it. If I keep it in the same directory the Makefile automatically links it with the http_client so-file, which is not what I want. I would like to store it somewhere - I can either commit is a module that doesn’t compile by default, store it in a hidden branch and forget about it or get help in fixing the Makefile so it can optionally compile in the same directory. Which would be the way forward? Right now it doesn’t do much more than bind to the API, but hopefully it will soon be able to test all the provided API functions. /O _______________________________________________ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-- Daniel-Constantin Mierla http://www.asipto.com - http://www.kamailio.org http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda