<br><br><div class="gmail_quote">On Nov 21, 2007 10:14 AM, David Malcolm <<a href="mailto:dmalcolm@redhat.com">dmalcolm@redhat.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="Wj3C7c">On Wed, 2007-11-21 at 09:35 -0500, Noah Gift wrote:<br>> I have a gigantic threaded beast I need to test, and I want to write<br>> functional tests that supplement the doctests and unittests, but
<br>> wanted some advice on the proper way to do this. I have not seen much<br>> documentation on writing non-web functional tests, my tool is a CLI<br>> tool. The basic thing I want to verify is that my tool creates a XML
<br>> file with the information I would expect to be there. For example, is<br>> there a selenium equivalent for command line tools?<br>><br></div></div>Have you tried the "expect" tool; see e.g.<br><a href="http://pexpect.sourceforge.net/" target="_blank">
http://pexpect.sourceforge.net/</a><br><br>Doesn't do recording AFAIK, but useful for invoking CLI tools in a<br>testing context<br></blockquote><div><br class="webkit-block-placeholder"></div><div>Dave,</div><div><br class="webkit-block-placeholder">
</div><div>I hadn't even thought of that, using pexpect is an interesting idea though. Recording command line tools seems like it could be a really cool open source testing project actually, now that I think about it more.... Maybe a Sprint for PyCon?
</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br><br>Hope this helps<br>Dave Malcolm<br><br><br></blockquote></div><br>