<div dir="ltr">In my opinion this would be a terrible waste of time for this case. To really test this you would have to setup Selenium (or similar) to test in a wide variety of OSes/Browsers. If the alternative is to bundle a handful of known working JS files with coverage...why bother?</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 3, 2014 at 6:59 AM, Daniel Staple -X (dastaple - BSKYB at Cisco) <span dir="ltr"><<a href="mailto:dastaple@cisco.com" target="_blank">dastaple@cisco.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> From: <a href="mailto:testing-in-python-bounces@lists.idyll.org">testing-in-python-bounces@lists.idyll.org</a> [mailto:<a href="mailto:testing-in-python-">testing-in-python-</a><br>
> <a href="mailto:bounces@lists.idyll.org">bounces@lists.idyll.org</a>] On Behalf Of Ned Batchelder<br>
> Sent: 03 March 2014 11:38<br>
> To: Ben Finney; <a href="mailto:testing-in-python@lists.idyll.org">testing-in-python@lists.idyll.org</a><br>
> Subject: Re: [TIP] Disable keyboard shortcuts in html coverage reports?<br>
<div><div class="h5">><br>
> On 3/2/14 10:32 PM, Ben Finney wrote:<br>
> > Ned Batchelder <<a href="mailto:ned@nedbatchelder.com">ned@nedbatchelder.com</a>> writes:<br>
> ><br>
> >> On 3/2/14 4:37 PM, Thomi Richards wrote:<br>
> >>> I've managed to track the problem down to the 'jquery.hotkeys.js'<br>
> >>> file. In Precise this is version '0.8', in trusty it's '0.8+'. […]<br>
> >> This sounds like the problem is not in coverage.py at all, but in the<br>
> >> jquery.hotkeys.js file it depends on? Perhaps Trusty shouldn't take a<br>
> >> new version, or you can get in touch with the developer?<br>
> > Ideally, you as the author of a library depending on<br>
> > “jquery.hotkeys.js”, should communicate with the author of that<br>
> > library to make sure newer versions continue to work with your dependent<br>
> code.<br>
> ><br>
> > If there are changes in the library (and changes so small they<br>
> > apparently don't warrant an increase in the version string) that cause<br>
> > dependent code to break, the library code and/or the dependent code<br>
> > needs to be fixed.<br>
> ><br>
> > Do you agree?<br>
> ><br>
> Actually, as you know, I was in favor of having my own copy of these tiny<br>
> jQuery libraries that I needed to make coverage.py work. You were in favor<br>
> of applying the Debian philosophy of making everything a separate library, no<br>
> matter how finely sliced. The theory was that I could automatically get fixes.<br>
> Now I've automatically gotten bugs. I had a package that worked. Debian<br>
> has a package that does not. Now I have to chase down the author? :(<br>
><br>
> Who made the decision to upgrade the package in Debian?<br>
><br>
> --Ned.<br>
<br>
</div></div>This may sound ludicrous but:<br>
* Packages have dependents in machine readable formats<br>
* Dependents can have automatic test suites. I'd be surprised if coverage.py didn't.<br>
* This could be run as automated testing with Travis or Jenkins.<br>
* There are a number of free open source test infrastructure providers.<br>
<br>
I am aware it is much more complicated than this and probably requires time to set up, but it wouldn't be unreasonable to suggest setting up a hook to trigger the coverage.py tests in Debian when the packages it depends on change. Perhaps when slicing so thinly - something like this is what would protect the packages from breaking like this.<br>
<br>
Danny<br>
<div class="HOEnZb"><div class="h5"><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>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>David<br>blog: <a href="http://www.traceback.org" target="_blank">http://www.traceback.org</a><br>twitter: <a href="http://twitter.com/dstanek" target="_blank">http://twitter.com/dstanek</a><div>
www: <a href="http://dstanek.com" target="_blank">http://dstanek.com</a></div>
</div>