When I run jpm test -b c:/programme/nightly/firefox.exe -v I get this at the end: console.warn: issue-pigeon: 4 warnings or errors were logged to the platform's nsIConsoleService, which could be of no consequence; however, they could also be indicative of aberrant behavior. 12 of 12 tests passed. All tests passed! JPM undefined JavaScript error: resource:///modules/CustomizableUI.jsm, line 157 0: TypeError: aWindowPalette is undefined See also http://stackoverflow.com/questions/29352326/how-to-view-jpm-console-warnings for another person wondering where to find these. Running jpm test -b c:/programme/nightly/firefox.exe -v --do-not-quit keeps the browser open from where I can open a Browser Console to find these errors and warnings and many others (another little challenge). In my case filtering for self.js in the Browser console did the trick: ReferenceError: reference to undefined property permissions['private-browsing'] self.js:58:0 ReferenceError: reference to undefined property permissions['private-browsing'] 2 self.js:58:0 ReferenceError: reference to undefined property permissions['private-browsing'] self.js:58:0 Would be nice if jpm could at the advice about --do-not-quit is its warning message, e.g. console.warn: issue-pigeon: 4 warnings or errors were logged to the platform's nsIConsoleService, which could be of no consequence; however, they could also be indicative of aberrant behavior. Add --do-not-quit and open a browser console to inspect these messages.

Because of the difficulty finding mentors and the expected life span of the SDK, we are removing [good first bug] from remaining SDK bugs.

Add-on SDK is no longer supported so resolving bugs as INCOMPLETE