Overall test coverage?

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Overall test coverage?

jewzaam
Administrator
Turns out it's 70%!

https://coveralls.io/r/lightblue-platform/lightblue

This includes these modules:
* lightblue-applications
* lightblue-audit-hook
* lightblue-client
* lightblue-core
* lightblue-ldap
* lightblue-migrator
* lightblue-mongo
* lightblue-rdbms
* lightblue-rest

The only other module we would want to include in this metric would be lightblue-puppet.  And we're stuck getting code coverage for puppet right now (see https://github.com/lightblue-platform/lightblue-puppet/issues/53)
Reply | Threaded
Open this post in threaded view
|

Re: Overall test coverage?

dhaynes
Reply | Threaded
Open this post in threaded view
|

Re: Overall test coverage?

lcestari
In reply to this post by jewzaam
Very nice. One thing that might be interesting as well is to extract some information from travis api and generate some statistics about it (for example the time to turn and PR build stable, if there were times where the code compiled for a JVM vendor and not for another one, the expected time of the compilation of the projects for each JVM, etc)
Reply | Threaded
Open this post in threaded view
|

Re: Overall test coverage?

jewzaam
Administrator
Maybe there's a project out there to get that info already?

On Mon Jan 26 2015 at 9:21:07 AM lcestari [via lightblue-dev] <[hidden email]> wrote:
Very nice. One thing that might be interesting as well is to extract some information from travis api and generate some statistics about it (for example the time to turn and PR build stable, if there were times where the code compiled for a JVM vendor and not for another one, the expected time of the compilation of the projects for each JVM, etc)


If you reply to this email, your message will be added to the discussion below:
To start a new topic under lightblue-dev, email [hidden email]
To unsubscribe from lightblue-dev, click here.
NAML