[ https://issues.jboss.org/browse/JBDS-3850?page=com.atlassian.jira.plugin.... ] Pavol Pitonak commented on JBDS-3850: ------------------------------------- [~dgolovin], [~jrichter1] these are my findings so far: * I found two live JS code coverage tools - [Istanbul|https://github.com/gotwarlost/istanbul] and [JSCover|http://tntim96.github.io/JSCover] * JSCover is implemented in Java, Istanbul is implemented in JavaScript * Istanbul seems to be preferred by JS community * Istanbul can be integrated with Mocha, Jasmine and Karma I suggest that we use *Istanbul* We have 3 types of tests that should generate code coverage statistics: # unit tests - multi-platform, they only need Node.js, launched using Mocha, run on _npm test_ # browser tests - multi-platform, they need Node.js, launched using Karma, they test Angular-specific code (directives etc), run on _npm test_ # ui tests - platform-specific, run with built installer binary, using Protractor, run on _npm run ui-test_ For now, I only focused on unit tests. I have PoC on my feature branch but # I was not able to run it with Babel 5 # when we want to upgrade to Babel 6, we either need to wait for JSPM 0.17 (cannot estimate when will be released) or remove JSPM completely (JBDS-3769) which is half-way done on my feature branch (only need to fix Karma tests) # when I removed JSPM, I still need to use latest development release of Istanbul (1.0.0-alpha.2) instead of latest stable release (0.4.3) [~dgolovin], [~jrichter1] how do we want to proceed? -- This message was sent by Atlassian JIRA (v6.4.11#64026)