This repository has been archived by the owner on May 29, 2019. It is now read-only.
document Travis CI automated tests configuration without Sauce Labs #2619
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.
Hi there,
I did struggle yesterday setting up automated testing on my PRs for my polymer project, so I thought adding the findings in the documentation would help more people finding the information quickly.
I am not going into too much details because I haven't experienced the need for it, but adding something about the custom
wct.conf.json
file could also be beneficial, for the reasons mentioned in this issue comment: https://github.com/Polymer/web-component-tester/issues/656#issuecomment-374068089