search

SoftwareMarbles / lazy

Hackable Coding Assistant
http://getlazy.org
MIT License
1 stars 0 forks source link

Create test-stats engine #16

Open ierceg opened 7 years ago

ierceg commented 7 years ago

Track stats of failed and succeeded tests and coverage results. To send the data create modules like mocha-lazy-reporter and lcov uploaders.

ierceg commented 7 years ago

Show coverage output in the editors just like we do for linters and PRs. In general the model should be to move everything behind lazy, no matter if lazy runs locally or in the cloud. Then lazy can constantly be doing something (e.g. running tests, coverage) assisting the developer. It could be done intelligently as well - don't trigger tests unless linters are passing, don't trigger coverage unless tests are passing, limit running tests and coverage on files that are NOT being edited at the moment.