Before submitting a pull request, please provide the following information:
What is it?
Automate build process
Publish code coverage metrics during build process
Add some boilerplate code to start testing React component
What was the root cause of the problem originally / what feature was missing?
Just as open source projects publish source code, test suite code coverage results should be published too. The mere act of publishing code coverage is a way to engage developers and users alike to improve such results. Without such stats, how can users have confidence that the project test suite is comprehensive? Bugs still crop up even with good code coverage, but so many bugs will be squashed during the development of a test suite that strives to exercise every line of source code.
How does this pull request solve it (in broad terms)?
Add build status and code coverage badges in README to quickly check the current status of those metrics
Does it close any open issues?
Closes #29
Quick checklist
[x] add Travis CI build configuration
[x] add boileplater code to test web-dapp components
TODO: define coverage goals so build fails if it is not enough
Additional information
Integration between Travis CI and converalls.io should work out-the-box for public repositories. In case it does not work try to set COVERALLS_REPO_TOKEN env variable for the corresponding repo configuration in Travis CI with the repo token generated when the repo is registered in coveralls.io.
Before submitting a pull request, please provide the following information:
What was the root cause of the problem originally / what feature was missing? Just as open source projects publish source code, test suite code coverage results should be published too. The mere act of publishing code coverage is a way to engage developers and users alike to improve such results. Without such stats, how can users have confidence that the project test suite is comprehensive? Bugs still crop up even with good code coverage, but so many bugs will be squashed during the development of a test suite that strives to exercise every line of source code.
How does this pull request solve it (in broad terms)? Add build status and code coverage badges in README to quickly check the current status of those metrics
Does it close any open issues? Closes #29
Quick checklist
TODO: define coverage goals so build fails if it is not enough