pr checks in travis and sauce labs #481
Merged
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.
Add execution of the unit tests and sample UI end-to-end tests on PR. However, in order to trigger such check you will have to enable the repository in travisCI and set up sauce labs account using environment variables. I will provide @rigor789 details about the settings in travis by mail including the temporary sauce labs account while you request access to a new one from them https://saucelabs.com/open-source.
The next step, I will be working on, is an execution of the tests using all available "next" versions of NativeScript modules. This way we will be sure that any new changes are not breaking nativescript-vue. For that purpose I will need you to create "next" branch where only the .travis.yml file will be different. However, we have to think about how to sync "next" with the "master" branch. We do this automatically for our plugins by using Jenkins job but in the context of nativescript-vue we may need to do it manually or somehow in travis if possible. We can talk about that in slack