-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
Moved xpath into boostrap java #3428
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
Conversation
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.
authorship is tracked via git
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.
Oops yeah. Those get added by my ide by default.
|
LGTM. Pretty sure @bootstraponline will ask you to remove the "created by jonahss" comments though :-) |
|
I'd like to do a better review on this once I'm back from the roadshow on Friday. |
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.
Do you know why?
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.
Because android UiAutomator library is notoriously flaky and error prone :(
|
ok. I think this is fine to merge. jlipps wants to release 1.2.2. I'll do a proper review later and that doesn't block the pr. |
|
also remember to squash to one commit |
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 do we need continue?
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.
I probably had code following the try/catch, which I later deleted.
It's nice to have the continue in there, so if a developer casually added some logic to that iteration, they wouldn't accidentally forget to add 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.
I don't think we should add a continue unless it's necessary. It's a for loop so we're going to continue either way.
|
looks like travis caught an error. I removed the npm dependency on I'll squash these commits. but does anything else need to be changed for merge? We can create a separate issue for adding stack-trace to errors. |
|
Looks good to me! Do all the appium xpath tests still pass with this? |
…s buggy and adheres to the full xpath spec. Finding by XPath now operates on the uncompressed xml hierarchy. Fixes appium#3307
|
squashed. Yup, appium xpath tests pass. |
I think it's fine. I don't think we need the continue, otherwise 👍 from me. |
|
agreed about the interesting |
…on the java side, not in node.
|
removed that |
Moved xpath into boostrap java
|
@Jonahss hey, you said you would squash. |
|
I guess it's about 3 different issues so the different commits are fine. |
|
I had time to test this today and it all seems to be working. It'd be nice to have the Java bootstrap tests run automatically if that's not already setup. |
|
Agreed. I'll create an issue. On Sun, Aug 24, 2014 at 7:42 PM, bootstraponline [email protected]
|
And removed complex-find while at it.
Submitting to @bootstraponline for review.
I'm working now on changing the getPageSource code to reuse the same code here.