<span class="gmail_quote"><br></span>Hi Noah,<br><br>Tell me, does it take time to generate the tests themselves, before you run them ?<br><br>That question may seem strange, so let me explain:<br><br>Point 1 : One way to create tests is to "yield" them from a testing function. This is a very powerful feature. Then you can generate your tests out of a database, for instance. You don't need to have your tests hardcoded. This may not seem a good idea in many cases, but it works quite well to check that all the content of a database is properly set up, for instance. One problem is that just creating the tests themselves may take time.
<br><br>Point 2 : One architecture I though we could implement is to have a "master nosetests" and a lot of "slaves nosetests". Each of them would have the same tests to run, BUT with the following algorithms:
<br><br>- The slaves, before running a test, would ask the master if they must or not (skip or not)<br>- The master would be here just to tell the slaves if they must / must not run the tests<br><br>That architecture may seem strange, but we actually have something very similar (with only one slave) with a special plugin of ours which handles crashes (released soon, hopefully). The master is just in charge of gathering the results and telling the slaves what to run; and the slave is in charge of running them. If the slave dies (because of a crash), it it restarted by the master, it gathers the same tests as before, but the master will not tell the slave to run the already-run tests.
<br><br>It should not be too difficult to generalize with a lot of slaves. But if gathering the tests takes time, that's a problem, because all slaves will have to do so.<br><br><div><span class="gmail_quote"> 2007/11/21, Noah Gift <
<a href="mailto:noah.gift@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">noah.gift@gmail.com</a>>:</span><div><span class="e" id="q_116c06a23ccc4718_1"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I have another "thing" I am working on where I am interesting in doing
<br>massive parallel testing as a current series of thousands of tests<br>takes over 24 hours. I am extremely ignorant of open source tools in<br>Python that do this already, but one Idea I had was to use parallel<br>python and to setup a bunch of testing nodes:
<br><br><a href="http://www.parallelpython.com/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.parallelpython.com/</a><br><br>Is there anything pre-built that someone could recommend? The Pyvix
<br>buildbot stuff seems interesting, but I am not sure if that directly
<br>applies for me.<br><br>Noah<br><br>_______________________________________________<br>testing-in-python mailing list<br><a href="mailto:testing-in-python@lists.idyll.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
testing-in-python@lists.idyll.org</a><br><a href="http://lists.idyll.org/listinfo/testing-in-python" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://lists.idyll.org/listinfo/testing-in-python</a><br></blockquote></span></div></div><span class="sg"><br><br clear="all"><br>-- <br>Laurent Ploix<br><a href="http://lauploix.blogspot.com/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://lauploix.blogspot.com/</a>
</span><br clear="all"><br>-- <br>Laurent Ploix<br><a href="http://lauploix.blogspot.com/">http://lauploix.blogspot.com/</a>