On Wed, Feb 26, 2014 at 5:01 AM, Stanislav Ochotnicky &lt;sochotnicky@redhat.com&gt; wrote:<br>
<blockquote type="cite"><div class="plaintext" style="white-space: pre-wrap;">
Because unit tests are designed to be run as part of the build
process. It's not impossible to run them *after* the build, but good
luck making it work reliably across all packages without manual work.</div></blockquote><br><div>The <a href="https://wiki.gnome.org/Initiatives/GnomeGoals/InstalledTests">https://wiki.gnome.org/Initiatives/GnomeGoals/InstalledTests</a></div><div>initative, as implemented by gnome-continuous, takes these "unit tests" as you call them and runs them as what you call integration tests. &nbsp;(Personally, I think distinguishing them is a broken idea. &nbsp;No one runs just one bit of software, they run a tree - a complete system)</div><div><br></div><div>For example, after glib changes, I rerun the *gtk* tests. &nbsp;After gtk changes, I rerun *application* tests.</div><div><br></div><div>This simple change of taking existing valuable tests that were run at once most per build and turning them into something run 50 or more times a day made them much more valuable. &nbsp;It also revealed many of them were full of race conditions...</div><div><br></div><div><br></div>