-
-
Notifications
You must be signed in to change notification settings - Fork 760
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
Addition to #545 #546
Addition to #545 #546
Conversation
- new annotations were provided - supporting tools were actualized
…a-client into TikhomirovSergey-xcuitFindBy
@TikhomirovSergey I see this is first time javadoc task is running in Travis job :) Its because of javadoc task refractor in build.gradle file :) |
@SrinivasanTarget The travis build is failed |
Yeah I have to find a way to ignore signing in Travis.
…On Sun 25 Dec, 2016, 6:41 PM Sergey Tikhomirov, ***@***.***> wrote:
@SrinivasanTarget <https://github.com/SrinivasanTarget> The travis build
is failed
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#546 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIfAJSvJxJZ56SQZ_P1l_nNG2Dvatbutks5rLmuWgaJpZM4LVYoy>
.
|
|
||
import java.io.File; | ||
|
||
public class AppXCUITTest extends BaseIOSTest { |
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.
👍
|
||
@iOSXCUITFindBy(className = "XCUIElementTypeSlider") | ||
private MobileElement slider; | ||
|
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.
@SrinivasanTarget
Everything is ok. But I think coverage could be enhanced. There is no case like
@iOSFindBy(id = "someId")
private MobileElement foundLikeIOSId;
because I think some locators (like "id") are compatible with both modes. It similar to the test of the selendroid mode.
@SrinivasanTarget Everything is ok but could you provide one more test as it was mentioned in remarks? |
Sure will do that :)
…On Sun 25 Dec, 2016, 6:52 PM Sergey Tikhomirov, ***@***.***> wrote:
@SrinivasanTarget <https://github.com/SrinivasanTarget> Everything is ok
but could you provide one more test as it was mentioned in remarks?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#546 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIfAJehhrhL11VKAPYF2RQv8IkB3Zaolks5rLm38gaJpZM4LVYoy>
.
|
|
||
@iOSXCUITFindBy(className = "XCUIElementTypeSlider") | ||
private MobileElement slider; | ||
|
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.
@SrinivasanTarget
Also you could add this test
@iOSFindBy(iOSAutomation = "some searching script")
@iOSXCUITFindBy(iOSNsPredicate = "some predicate") //it should be used for the searching instead of
//@iOSFindBy
private MobileElement foundByScript;
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.
@SrinivasanTarget @TikhomirovSergey when we initialize IOSDriver and provide the XCUITest as AutomationName only this case will it pick the iOSXCUITFindBy ?
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.
@saikrishna321 When there is only java @iOSFindBy
then it will be used.
When there are
@iOSFindBy
@iOSXCUITFindBy
then java @iOSXCUITFindBy
will be preferred. Selendroid mode works the same way.
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.
@TikhomirovSergey it works that way in Selendroid, coz the automatioName is set to selendroid. It should be the same here as well, if the automatioName is set to XCUITest only then @iOSXCUITFindBy should be preferred. Thoughts ?
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.
@saikrishna321 Yes you are correct. Btw for iOS10 automationName is not mandatory, server will set automatically even if you have given platformVersion.
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.
@saikrishna321 I can't get...
It is designed the same way as java @AndroidFindBy
/java @SelendroidFindBy
. It was designed this way because it is possible that old automation for iOS <= 9.3 and the new automation should be supported by one test scope.
The algorithm:
@iOSFindBy
@iOSXCUITFindBy
if you run new mode then
@iOSXCUITFindBy
is used. If you use legacy mode then
@iOSFindBy
is used instead.
@iOSFindBy
is used by both modes.
@iOSXCUITFindBy
is used by the new mode. If you launch legacy mode then page object tools create
ByIdOrName
The same works for Android/Selendroid.
So what the concern?
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.
@TikhomirovSergey no concern, well explained. Cheers
@SrinivasanTarget |
Codacy is GREEN now. Will try to fix travis. |
@SrinivasanTarget Yes. Everything is ok. Please get build successful |
@TikhomirovSergey Yeah Sure.Its weird. I don't see travis running our command. Command works locally fine. |
@TikhomirovSergey Travis is GREEN now. Its running our commands now. Moved it to run under container based infra. |
Linking gists justs for internal reference: iOS 10 - https://gist.github.com/SrinivasanTarget/a75db7dfcff1e237ae6ad9919ffa8219 |
Change list
Types of changes
What types of changes are you proposing/introducing to Java client?
Put an
x
in the boxes that apply@TikhomirovSergey FYI