-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add airtap for continuous browser tests #340
Conversation
.airtap.yml
Outdated
version: -3..latest | ||
- name: firefox | ||
version: -3..latest | ||
# - name: safari |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wasn't sure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if they are passing, let's go for it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We won't know until you merge ;) I didn't run the tests on my own SL account or anything.
I'll uncomment safari and we'll see.
I would like to ask them to bump it, after this lands. |
Can you please allow me to push to this branch? I've made some changes in the next branch, and I would like to push a rebase. |
I'm currently getting:
When running things locally. Then it's stuck there. |
@ralphtheninja mind helping out with the airtap error above? I'm short on time |
Also on Travis we are getting: "Skipping Airtap due to no secure Travis environment" Why is that happening? |
@mcollina Travis secure environment variables are not available in PRs from external forks. Airtap doesn't run in this case because it would error (due to missing Sauce Labs credentials). |
Oh ok. So I should really just test it locally and then push to a new branch. |
By locally do you mean in a local browser, or Sauce Labs? Because Airtap does not support the latter (yet), unless you manually run a Sauce Connect tunnel. See airtap/airtap#23 |
@@ -24,6 +25,8 @@ | |||
"scripts": { | |||
"test": "tap -j 4 test/parallel/*.js test/ours/*.js", | |||
"ci": "TAP=1 tap test/parallel/*.js test/ours/*.js | tee test.tap", | |||
"test-browsers": "airtap --sauce-connect -- test/browser.js", | |||
"test-browser-local": "airtap --local --open -- test/browser.js", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
.travis.yml
Outdated
@@ -22,5 +22,5 @@ matrix: | |||
script: npm run $CMD | |||
env: | |||
global: | |||
- secure: nk/kDUZV385ey9kkrGi6EHvnslTAW+GEHGrjbFIsb8Foq01bL9oj0uPaVc5kaVWCHst3WsIdVMA1Hos/lN/WMHRyfOiSrVVWv0sVnzg0YaM9cBbn5jwXn30Z645REgQcoEDKrYFp8rE3RpPFgYDFWNh948qwPtwtnwNhoq/Gd9A= | |||
- secure: faODkEUSlbH4fLBll4UkHeSEsCZdW+Hw+Sb6yDX5PXkIgq5wvqALIUgDIEBz2F8gciLlPlIssR2csKPqYIK5uwUq7uPBJVmwcf6i0K9NZaU/WaGaUVCzs2oMAoN007pTU30USEiWzfEGR+0d5hRKoeJdZIU0nBxkpLY4ZWM0SGU= | |||
- secure: MMYiNZ8ICzNkz1OQ3/jFrcBVxG5eIGoUn1/IRL9JeWbB6gWg8kxAMFXZmLDJrJj5Zm6VD31mpX6PS3Ot46syMl+FnnyNCdqcCJUuUYCdRS8PanUnVq2QL1+9f2uT/S3UeQJhTaFXAzHA4cSNcaXlSB0QzbiDi0xZUobAAM/h5sw= |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mcollina This worked, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No it was skipped.
Skipping Airtap due to no secure Travis environment.
Made a few quick hacks to get most tests passing in local Chrome at least.
What's the concurrency limit of the Sauce Labs account? You may want to change Travis's concurrency setting depending on that.