<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Life is grand - Latest Comments in Javascript code coverage MIA</title><link>http://lifeisgrand.disqus.com/</link><description></description><language>en</language><lastBuildDate>Wed, 27 Dec 2006 16:42:25 -0000</lastBuildDate><item><title>Re: Javascript code coverage MIA</title><link>http://paulmwatson.com/journal/2006/10/04/javascript-code-coverage-mia/#comment-1281264</link><description>JavaScript Coverage Validator left beta in late October.&lt;br&gt;&lt;br&gt;&lt;a href="http://www.softwareverify.com/news.html" rel="nofollow"&gt;http://www.softwareverify.com/news.html&lt;/a&gt;&lt;br&gt;&lt;br&gt;Added Firefox 2 support in November&lt;br&gt;&lt;br&gt;&lt;a href="http://www.softwareverify.com/blog/" rel="nofollow"&gt;http://www.softwareverify.com/blog/&lt;/a&gt;&lt;br&gt;&lt;br&gt;Stephen</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Stephen Kellett</dc:creator><pubDate>Wed, 27 Dec 2006 16:42:25 -0000</pubDate></item><item><title>Re: Javascript code coverage MIA</title><link>http://paulmwatson.com/journal/2006/10/04/javascript-code-coverage-mia/#comment-1281263</link><description>This doesn't help you with your Javascript problem but Cobertura4J2ME does work quite well now on mobile java code.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brian W</dc:creator><pubDate>Tue, 10 Oct 2006 12:08:13 -0000</pubDate></item><item><title>Re: Javascript code coverage MIA</title><link>http://paulmwatson.com/journal/2006/10/04/javascript-code-coverage-mia/#comment-1281262</link><description>Ah I see.  It precludes you from determining the answer statically, is all I meant (i.e. you can't just have a tool that looks at the code and figures it out).  It can of course do it in the way you describe.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andy Peace</dc:creator><pubDate>Sat, 07 Oct 2006 07:35:18 -0000</pubDate></item><item><title>Re: Javascript code coverage MIA</title><link>http://paulmwatson.com/journal/2006/10/04/javascript-code-coverage-mia/#comment-1281261</link><description>How does JavaScript having closures preclude it from code coverage analysis? Ruby has closures and it has some decent code coverage tools.&lt;br&gt;&lt;br&gt;AFAIK most CC tools inject traces into the code and then run the tests, so computing what gets run and what does not.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Watson</dc:creator><pubDate>Fri, 06 Oct 2006 04:19:06 -0000</pubDate></item><item><title>Re: Javascript code coverage MIA</title><link>http://paulmwatson.com/journal/2006/10/04/javascript-code-coverage-mia/#comment-1281260</link><description>Since JavaScript has closures, I think it's impossible to compute (though may be wrong).  You could do it dynamically (i.e. run the scripts for a long time and see what happens) but it's not guaranteed to be correct.  You could also get a conservative approximation using standard algorithms.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andy Peace</dc:creator><pubDate>Thu, 05 Oct 2006 13:29:50 -0000</pubDate></item><item><title>Re: Javascript code coverage MIA</title><link>http://paulmwatson.com/journal/2006/10/04/javascript-code-coverage-mia/#comment-1281259</link><description>I'm hearing some rumblings too that a similar problem exists with J2ME code coverage tools. Apparently, there is an extension to Cobertura but it does not work correctly (yet).</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">James Mernin</dc:creator><pubDate>Wed, 04 Oct 2006 07:56:03 -0000</pubDate></item></channel></rss>