celix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pepijn Noltes <pepijnnol...@gmail.com>
Subject Re: Coveralls Test Coverage Integration
Date Mon, 12 Oct 2015 18:40:23 GMT
Hi,


On Sat, Oct 10, 2015 at 9:19 PM Bjoern Petri <bjoern.petri@sundevil.de>
wrote:

>
> Hi everyone,
>
> A while ago we started using Travis CI to ensure that Celix including
> all bundles is still building after a commit has been pushed. Within the
> last week we committed some patches to fix the current unit testing
> setup and there are some more to come (Thanks to Menno!). Therefore, I
> also enabled the unit testing within the Travis configuration.
>
> An hour ago, I extened this with the integration of Coveralls. Coveralls
> is a web service that is able to keep track of our automated test
> coverage. It is similar to the html report which is generated by the
> 'make coverage' target, but just web based and - thanks to Travis -
> fully automated.
>
> Currently, only the develop branch pushes the test coverage results to
> Coveralls. If you want to enable Coveralls in your feature branch, just
> take a look at the current setup in out Travis configuration.
>
> See our current code coverage (for the utils library):
> https://coveralls.io/github/apache/celix
>


Nice work. I think this really benefits the development of Celix, keeping
the builds successful and more focus on code coverage.
That said I think it would also be good to have a more realistic overview
of the code coverage, not only the utils ;).







>
> Regards,
> Bjoern
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message