desktop
desktop copied to clipboard
Musicoin
Write proper tests
With the increasing number of facilities that the wallet offers, it becomes critical not to break certain features when introducing new ones. Towards this, we have to write test cases and test them using a CI (Travis/Circle would be fine I guess, Jenkins is also OK). Ideas welcome
Upgrading the bounty on this one to 20k MC, which can be expanded upon in the future.
Okay, if all goes according to plan, I should be able to hook this nicely into a further minor bump after the yarn patch; so that yarn test is all you need to do; and I'll TRY to make a little menu for adding a new test. I have no idea why the ease of contributing is so important to me; but it really is.
tests are very, very important. it has been a few years sense i have written any good ones, last ones i did i used shoulda on RoR, along with a more complex suite that actually ran client side javascript (sometimes in a browser even).
does anyone have any specific plans for what we are going to do here? at least as far as which testing frameworks/suites/whatever they should be callled
@movingelectrons I was considering doing scripted browser tests, considering that it does run on a browser's core.
do you know if it is possible to start the app on the actual chrome browser?
I wanted to know if its easy to run it in a browser, or at very least the UI, so I can use the developer tools in chrome to tweak the css and html. Doing it that way will save me a good chunk of time for certain.
@movingelectrons As far as I'm aware - for now - there's just the dev tools in the sdk version of nw.
Bumping up the bounty on this one to 30k MC for anyone that manages to get an integrated framework ready.