You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 26, 2020. It is now read-only.
With limited time over the summer and a conflicting lust to participate in this, maybe this is a small problem I can assist with in the coming months.
Do we need large automation systems like jenkins/buildbot or could something built ourselves do the trick, something like hack of cron and some scripting? The reason I ask this is because I haven't built it myself yet so I don't know how many processes goes into it and how the testbench is performed.
I was thinking along the lines of using Istanbul's NYC and coveralls. I don't think it should be too crazy to setup. We already use Travis and are in the process of setting up appveyor, so testing isn't a problem, there really aren't many tests at this point though.
Is there any tests at all written today? I can make a PR with nyc and coveralls, but as far as I understand the only tests that runs within the npm test commands are electrons internal tests? When I run the coverage I get 0. But at least there's something to start with. :-)
It has become apparent that we need proper automated testing and code coverage reports. This issue is a request for the latter.
The text was updated successfully, but these errors were encountered: