<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 6 February 2014 09:30, Mateusz Łoskot <span dir="ltr"><<a href="mailto:mateusz@loskot.net" target="_blank">mateusz@loskot.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="im">On 6 February 2014 01:51, John McNamara <<a href="mailto:jmcnamara13@gmail.com">jmcnamara13@gmail.com</a>> wrote:<br>
><br>
> The tutorial is here:<br>
><br>
> <a href="http://pytest_c_testrunner.readthedocs.org" target="_blank">http://pytest_c_testrunner.readthedocs.org</a><br>
<br>
</div>What a great utility!<br>
I'll try it as soon as I have a moment.<br>
<br>
By the way, shouldn't "Pytest & C' read 'Pytest & C/C++' and so on?<br></blockquote><div><br></div><div>Hi Mateusz,<br><br></div><div>C++ tests could be supported in the same way. However C++ has a larger set of established test frameworks and test runners such as GoogleTest and Boost::Test. So I think it would be hard to make the case for using pytest with any of those.<br>
<br></div><div>C testing is generally a little more adhoc with a lot more bespoke testing code. Even then I'd admit that the case for using pytest is a little weak.<br><br></div><div>The tutorial stems more from an experiment to see if it could be done rather than a pressing need.<br>
<br></div><div>But any feedback is welcome.<br><br></div><div>John<br></div><div>-- </div></div><br></div></div>