coviolations.io now beta

coviolations.io - a service for visualizing test results and code analyzers today has moved to the beta stage.

Main innovations:

• support of private repositories and repositories of companies;
• xUnit support, coverage, jslint;
• setting the status of commits on github;
• adding annotations to the github code with the results of pep8 and jslint;
• adding a brief summary to the pull request (only with travis-ci);
• new fancy interface on AngularJS;
• nofail , nocomment and stderr parameters in .covio.yml .

Github integration

This update has improved github integration: now coviolations works with your private repositories and company repositories available to you.


The status of commits is set down (visible only in comparison of commits and pull request):

')
Errors and warnings in the annotations to the code:


Summary for pull request:

New fancy interface

The client part was rewritten from backbone.js to AngularJS. This allowed to throw out ~ 900 lines of code .

A dashboard has appeared:


New display of one task:


The success of pushing depending on the day of the week and part of the day:

xUnit, coverage, jslint and covio.yml

There is support for xUnit, coverage and jslint. For example .covio.yml with all of them:

 violations: jslint: jslint static/js/*.js coverage: coverage report xunit: cat xunit.xml 

Now you can do so that the “analyzer” does not affect the status of the task. For example, for pip-review:

 violations: pip_review: command: pip-review nofail: true 

You can take the result from stderr. For example, for python unittest and django:

 violations: py_unittest: command: ./manage.py test stderr: true 

And you can disable commenting code on github, for example, for jslint:

 violations: jslint: command: jslint static/js/*.js nocomment: true 

Links

coviolations.io
read the docs documentation
server source code
client source code