Dear Yoav<div><br></div><div>Could you explain what made you consider pyFit and Robot an "overhead compare to the benefit" ? That may help people suggest other alternatives... (and maybe consider building another framework if they agree)</div>
<div><br></div><div>laurent</div><div><br><div class="gmail_quote">2009/7/27 yoav glazner <span dir="ltr"><<a href="mailto:yoavglazner@gmail.com">yoavglazner@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div dir="ltr"><div>Hi all,</div>
<div> </div>
<div>I don't know if this is the place to ask but...</div>
<div>I'm a part of a team that writes a production system in python with wxPython and sqlElixir, </div>
<div>and i wanted to ask how do big projects in python do acceptance's test.</div>
<div> </div>
<div>we tried PyFit and Robot but found them an overhead compare to the benefits.</div>
<div> </div>
<div>if anyone has insight on this matter i would love to hear.</div>
<div> </div>
<div>BTW- we are using pymock/nose for unittesting and we are very happy with it.</div>
<div> </div>
<div>Thanks,</div>
<div>Yoav.</div></div>
<br>_______________________________________________<br>
testing-in-python mailing list<br>
<a href="mailto:testing-in-python@lists.idyll.org">testing-in-python@lists.idyll.org</a><br>
<a href="http://lists.idyll.org/listinfo/testing-in-python" target="_blank">http://lists.idyll.org/listinfo/testing-in-python</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Laurent Ploix<br><br><a href="http://lauploix.blogspot.com/">http://lauploix.blogspot.com/</a><br>
</div>