-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
run UI tests in drone on Firefox #31325
Conversation
Codecov Report
@@ Coverage Diff @@
## master #31325 +/- ##
=========================================
Coverage 64.84% 64.84%
Complexity 18324 18324
=========================================
Files 1198 1198
Lines 69580 69580
Branches 1283 1283
=========================================
Hits 45120 45120
Misses 24086 24086
Partials 374 374
Continue to review full report at Codecov.
|
3d866f0
to
63d342e
Compare
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.
LGTM
I suggest that we remove Firefox test matrix entries from Travis.
chrome, IE11 and Edge on nightly Travis should be plenty, and Firefox will happen with every PR.
This will make another 14 matrix jobs in drone PR builds. |
drone says it passed, but no codecov status has come. what happened??? |
@ownclouders rebase |
Hey! I'm GitMate.io! This pull request is being rebased automatically. Please DO NOT push while rebase is in progress or your changes would be lost permanently |
63d342e
to
146cae0
Compare
Automated rebase with GitMate.io was successful! 🎉 |
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.
Please do not merge - see further comments
Exactly - I am against having both browsers being tested during a PR test run. It will just add unnecessary build time to pull requests. I see testing different browser being deferred to async runs (nightly / weekly). The mechanism for this is in the works. You might be just a little bit ahead of your time ;-) Personally I would keep this open and revive once the mechanisms are in place. We can at the same time investigate how we can also add browserstack onto drone for the nightly/weekly scenarios |
af3547a
to
bea7b3a
Compare
rebased, made Firefox tests run on HTTP and skipped failing tests |
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.
Firstly, just 2 questions.
@@ -515,6 +526,18 @@ services: | |||
when: | |||
matrix: | |||
USE_SERVER: true | |||
SERVER_PROTOCOL: https | |||
|
|||
server: |
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.
This has the same pipeline step name as server:
above.
Only 1 of them ever gets started, but does it cause some confusion for drone.yml parsing?
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 confusion for drones, only for humans
we need to have the same name because that becomes the hostname for that service and it should be the same for HTTP and HTTPS, to have less confusion
@@ -529,6 +552,18 @@ services: | |||
when: | |||
matrix: | |||
USE_FEDERATED_SERVER: true | |||
SERVER_PROTOCOL: https | |||
|
|||
federated: |
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.
Same here, repeating the federated:
step
Maybe for now we could merge all the:
|
or running all |
Lots of code changes and discussion, so review is needed again
2ebc4bb
to
3c4ce3d
Compare
3c4ce3d
to
a5f69f6
Compare
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.
LGTM
And we can have a followup issue to investigate the test scenarios tagged skipOnFirefox
and try to find out why they fail (real problem on Firefox or Firefox webDriver "feature"...)
Just a minor note - the firefox container seems to be quite old Line 507 in a5f69f6
And it was last built 12 months ago:
|
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.
Please use a more recent firefox version
@patrickjahns see original description a newer version is not possible because of not finished implementations in the libraries
|
not possible currently due to limitations in libraries
@phil-davis issue opened for skipped tests #34491 |
@patrickjahns issue to update to a newer version of Firefox #34493 |
backport in #34494 |
Description
run UI tests in drone on Firefox without using saucelabs
by using the selenium docker containers we are able to run tests in Firefox same as we do in Chrome. This PR
Limitations:
enablePassThrough
option. So without changing the docker container we are limited to Firefox 58.0Motivation and Context
get more independent of travis & saucelabs
How Has This Been Tested?
🤖
Types of changes
Checklist: