-
Notifications
You must be signed in to change notification settings - Fork 155
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run acceptance tests on firefox #1213
Conversation
eabb7c0
to
6e8ede9
Compare
6e8ede9
to
49cda80
Compare
FF is crashing
will restart the build to see how often it happens |
if (value.ELEMENT) { | ||
webElementIdList.push(value.ELEMENT) | ||
} else { | ||
webElementIdList.push(value['element-6066-11e4-a52e-4f735466cecf']) |
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.
is that magic number always the same?
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.
Yes, you can read more about it here: https://www.w3.org/TR/webdriver/#elements
49cda80
to
6fb00b5
Compare
45e274e
to
0020c64
Compare
f1348ca
to
3b5b85d
Compare
32a7d90
to
3fc782c
Compare
There is an error in some suites with an error message { state: 'unknown error',
sessionId: null,
value:
{ systemInformation: 'System info: host: \'606a6335e49d\', ip: \'172.17.0.10\', os.name: \'Linux\', os.arch: \'amd64\', os.version: \'4.4.0-148-generic\', java.version: \'1.8.0_212\'',
message: 'Failed to decode response from marionette',
error:
[ 'Build info: version: \'3.141.59\', revision: \'e82be7d358\', time: \'2018-11-14T08:25:53\'',
'System info: host: \'606a6335e49d\', ip: \'172.17.0.10\', os.name: \'Linux\', os.arch: \'amd64\', os.version: \'4.4.0-148-generic\', java.version: \'1.8.0_212\'',
'Driver info: driver.version: unknown' ] },
status: 13 } Which might be caused due to memory problem in drone, Edit: Usually this occurs in the same suites, and other suites seem to pass without a problem |
3fc782c
to
65dd0bc
Compare
903c908
to
9ec0e8b
Compare
9ec0e8b
to
fca2f92
Compare
fca2f92
to
a738fb4
Compare
e0e6f38
to
3d28ac4
Compare
Another problem while running tests in firefox is that the user gets logged out when running In case of When the user receives a share and then receiver searches for the file the file seems to be already available to the user. Which means we can remove |
d772947
to
cb014b0
Compare
cb014b0
to
0140d0c
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.
all in all this looks a bit haky to me and might make the tests more flaky in the future. Should we maybe just archive this and try again in a couple of month?
| "^#29][29@({" | | ||
| "+-{$(882)" | | ||
| "home" | | ||
# Scenario Outline: Create a folder using special characters |
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.
why commenting that whole test out?
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.
That's a mistake, that should have@skipOnFIREFOX
BROWSER: chrome | ||
|
||
firefox: | ||
image: selenium/standalone-firefox-debug:3.141.59-mercury |
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.
why not :latest
?
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.
Oh, I used for testing purpose. I should keep the latest
one there.
Yeah its haky, we have skipped many scenarios that are failing on firefox without knowing the actual |
Closing this for now. We can retry after mozilla/geckodriver#285 is fixed. |
Description
Run acceptance tests on firefox
moveToElement()
is removed because it causes'move target out of bounds'
on firefox.According to documentation when running
click()
methodSo, the tests should still function as usual.
Related Issue
Fixes #1197
Motivation and Context
Make the tests more robust.
How Has This Been Tested?
馃
Screenshots (if appropriate):
Types of changes
Checklist: