#1091 - Adds travis for automated tests #1668
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Also fixes some of the test failures.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a .travis.yml file for running automated tests, this make it so that we can at least run unit tests.
Because the eslint still fails, I don't know if the karma tests work yet, but I have no idea how to further fix the eslint warnings (the multiple return type things are difficult to figure out).
See the results at https://travis-ci.org/borisson/Inputmask/builds/263046650, you should create a (free) https://travis-ci.org/ account and link it to this repository, preferably this should be configured to also test all Pull Requests.
If you can figure out how to get all eslint warnings/errors to pass and need help to configure travis for the karma tests just ping me (here or on twitter).
Doing this and improving the unit test coverage should make contributing easier.