Note that there are some explanatory texts on larger screens.

plurals
  1. POCode Coverage tool for BlackBerry
    text
    copied!<p>I'm looking for a <a href="http://en.wikipedia.org/wiki/Code_coverage" rel="nofollow noreferrer">code coverage</a> tool that I can use with a BlackBerry application. I'm using J2ME-Unit for Unit Testing and I want to see how much of my code is being covered by my tests.</p> <p>I've tried using <a href="http://www.cobertura4j2me.org/" rel="nofollow noreferrer">Cobertura for J2ME</a> but after days of wrestling with it I failed to get any results from it. (I believe that the instrumentation is un-done by the RAPC compilation). And despite <a href="http://blog.dreameffect.org/2008/09/25/cobertura-for-j2me-is-not-dead/" rel="nofollow noreferrer">this message</a>, the project seems to be dead.</p> <p>I've looked at <a href="http://code.google.com/p/jinjector/" rel="nofollow noreferrer">JInjector</a> but the project seems <em>very</em> incomplete. There is little (if any) documentation and although it <em>claims</em> to be able to work with BlackBerry projects, I haven't seen any places where it <em>has</em> been used for that purpose. I've played with the project quite a bit but to no avail.</p> <p>I've also tried the "Coverage" view in the BlackBerry JDE, even though I use Eclipse for development. The view stays permanently blank, regardless of clicking "Refresh" and running the application from the JDE.</p> <p>I've looked at <a href="https://stackoverflow.com/questions/39329/what-is-your-favourite-code-coverage-tools-free-and-non-free">most of the tools on this SO thread</a>, but they won't work with J2ME/BlackBerry projects.</p> <p><strong>Has anyone had any success with any code coverage tools on the BlackBerry?</strong> If so, what tools have you used? How have you used them?</p> <p>If anyone <em>has</em> managed to get JInjector or Cobertura for J2ME to work with a BlackBerry project, what did you have to do to get it working?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload