Closed svrooij closed 4 years ago
I think we could spend some time working on the test coverage. Right now there's like one big file, and it looks like it'd be pretty hard to make changes in there. Could we maybe break the tests up? I'd suggest a convention of tests stored close to the relevant files, i.e. in __test__
folders. Personal choice would be switching to jest?
This poll wasn't about test coverage, but you're right about the test part.
I think we could spend some time working on the test coverage. Right now there's like one big file, and it looks like it'd be pretty hard to make changes in there. Could we maybe break the tests up? I'd suggest a convention of tests stored close to the relevant files, i.e. in
__test__
folders. Personal choice would be switching to jest?
This poll wasn't about test coverage
This was meant as a comment to your original point:
This library doesn't have a high test coverage, so having a beta would allow other contributors to get their changes merged quicker.
I'm all for a beta branch. But if contributions are not happening because of lack of test coverage, I'd be willing to put in some work to increase that also. That's all.
I've created a alpha
branch but the NPM_TOKEN still has to be setup see #480
Since @bencevans added the NPM secret we can now release much faster. Choose for auto releases from the alpha branch for now, and then once in a while we push all the changes from alpha to master.
The alpha release might break sometime!!
Should we have a beta branch with a beta release?
A lot of libraries have a special branch setup do to small beta releases that get pulled to master once in a while. Do you think node-sonos should also implement that strategy?
Votes
Also comment your thoughts please.
Related to: