<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 02 Jun 2016, at 09:15, Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com" class="">miconda@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" class="">
<div bgcolor="#FFFFFF" text="#000000" class=""><p class=""><br class="">
</p>
<br class="">
<div class="moz-cite-prefix">On 02/06/16 09:09, Olle E. Johansson
wrote:<br class="">
</div>
<blockquote cite="mid:EF476B92-16D8-4D48-A537-AC3CA5FD5CF3@edvina.net" type="cite" class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On 01 Jun 2016, at 08:43, Daniel-Constantin
Mierla <<a moz-do-not-send="true" href="mailto:miconda@gmail.com" class="">miconda@gmail.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" class="">
<div bgcolor="#FFFFFF" text="#000000" class=""><p class="">Hello,</p><p class="">this probably needs a more elaborate
discussion and planning, being somehow related to unit
testing that is planned to be approached for 5.0.</p><p class="">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.</p>
<div class=""><br class="">
</div>
</div>
</div>
</blockquote>
Let’s create a module_test directory that hosts various test
modules then. Naming the directory “test” makes it clear for
users that it’s</div>
<div class="">not a normal production-use directory. I think creating test
modules for modules that implement API is a good thing. If we
can automate</div>
<div class="">tests that’s even better. I’ll use this module as a test case
and we’ll figure it out.</div>
<div class=""><br class="">
</div>
<div class="">If we come up with something else and need to move it, users
should not be affected, only developers. I know that we are a
grumpy</div>
<div class="">group of persons that doesn’t want to change anything, but
let’s hope that we can survive us messing around with test code
:-)</div>
</blockquote>
There is a folder 'test' now where are also the current units.
Perhaps is the best place where to create the new folder for testing
modules.<br class=""></div></div></blockquote>Ok</div><div>test/modules/src for source code</div><div>test/modules/cfg for test configurations</div><div><br class=""></div><div>?</div><div><br class=""></div><div>/O<br class=""><blockquote type="cite" class=""><div class=""><div bgcolor="#FFFFFF" text="#000000" class="">
<br class="">
Cheers,<br class="">
Daniel<br class="">
<br class="">
<blockquote cite="mid:EF476B92-16D8-4D48-A537-AC3CA5FD5CF3@edvina.net" type="cite" class="">
<div class=""><br class="">
</div>
<div class="">/O<br class="">
<blockquote type="cite" class="">
<div class="">
<div bgcolor="#FFFFFF" text="#000000" class=""><p class="">Cheers,<br class="">
Daniel<br class="">
</p>
<br class="">
<div class="moz-cite-prefix">On 31/05/16 22:46, Olle E.
Johansson wrote:<br class="">
</div>
<blockquote cite="mid:3B4C66D3-9ADB-4A96-B35B-52B746267EC3@edvina.net" type="cite" class="">
<pre class="" wrap="">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
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:sr-dev@lists.sip-router.org">sr-dev@lists.sip-router.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a>
</pre>
</blockquote>
<br class="">
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.asipto.com/">http://www.asipto.com</a> - <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.kamailio.org/">http://www.kamailio.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://twitter.com/#%21/miconda">http://twitter.com/#!/miconda</a> - <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a></pre>
</div>
_______________________________________________<br class="">
sr-dev mailing list<br class="">
<a moz-do-not-send="true" href="mailto:sr-dev@lists.sip-router.org" class="">sr-dev@lists.sip-router.org</a><br class="">
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br class="">
</div>
</blockquote>
</div>
<br class="">
</blockquote>
<br class="">
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla
<a class="moz-txt-link-freetext" href="http://www.asipto.com/">http://www.asipto.com</a> - <a class="moz-txt-link-freetext" href="http://www.kamailio.org/">http://www.kamailio.org</a>
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda">http://twitter.com/#!/miconda</a> - <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a></pre>
</div>
</div></blockquote></div><br class=""></body></html>