Weighing in...<div><br></div><div>I prefer option 1.<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
A specific problem is that we tend to test functionality of an<br>
enhancement not necessarily how that enhancement integrates with the<br>
eco-system of Koha and its these kind of conflicts that tend not to<br>
surface until its been deployed in the real world.<br></blockquote><div><br></div><div>This is a huge issue, and while it is not entirely solvable, we can definitely do *better*. Part of the problem is conflicting expectations, which we can&#39;t automate out of existence, but part of the problem is regression, plain and simple. One of the lowest impact ways to reduce regression is automated regression testing, which we can do, for example, with WWW::Mechanize. The tests are dead simple to write, and fantastically useful. There&#39;s even a wiki page about interface testing using WWW::Mechanize: <a href="http://wiki.koha-community.org/wiki/Interface_testing_with_WWW::Mechanize">http://wiki.koha-community.org/wiki/Interface_testing_with_WWW::Mechanize</a></div>
<div><br></div><div>Regards,</div><div>Jared</div></div><div><br></div>-- <br>Jared Camins-Esakov<div>Bibliographer, C &amp; P Bibliography Services, LLC</div><div>(phone) +1 (917) 727-3445</div><div>(e-mail) <a href="mailto:jcamins@cpbibliography.com" target="_blank">jcamins@cpbibliography.com</a></div>
<div>(web) <a href="http://www.cpbibliography.com/" target="_blank">http://www.cpbibliography.com/</a></div><br>
</div>