Run tests on CI - Githubissues

device-hackers / browser-ui-state

Small ~5 Kb (gzip) library which allows to determine current state of the browser's own UI (address bar, on-screen keyboard, etc)

http://browser-ui-state.surge.sh

MIT License

6 stars 3 forks source link

Run tests on CI #6

Closed vyshkov closed 6 years ago

vyshkov commented 6 years ago

You should run your tests on the travis CI before build, so if it fails - then it marks you commit with X - cross icon.

TheBit commented 6 years ago

Yeah, of course, I just don't know yet what is the best way to organize this :). Should I just add "test" script command inside "build" command? But I think there could be some other, more organic ways, I see there are some lifecycles, etc https://docs.npmjs.com/misc/scripts

TheBit commented 6 years ago

Done, example of failed commit and build:

https://github.com/device-hackers/browser-ui-state/commits/master (854e7cfe262e390875a55a300ec8006a3c31694d)
https://travis-ci.org/device-hackers/browser-ui-state/builds/289942140