<p>The unittest skipIf decorators are the simplest things for skipping individual tests / test cases. You could also group them and skip entire platform specific modules.</p>
<div class="gmail_quote">On Jul 12, 2012 12:09 PM, "andrea crotti" <<a href="mailto:andrea.crotti.0@gmail.com">andrea.crotti.0@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm writing a very complicated system that has to interact with<br>
databases, filesystems and perforce.<br>
<br>
I have a mock database using an in memory sqlite, and I'm studying some<br>
other ways to manage the filesystem, but I also have some tests that use<br>
the real db and real filesystem.<br>
<br>
Now I would like to have a way to mark them, for example I might want to<br>
run certain things only on Linux, other only on Windows, maybe on Linux<br>
I want to use the real database, on Windows the fake one..<br>
<br>
What might be a good way to achieve this (I use nosetest + mock + coverage)?<br>
<br>
Subclassing unittest.TestCase?<br>
Or maybe using decorators?<br>
Any other ideas?<br>
<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>
</blockquote></div>