How we use Appium as our product's core library
Appium is very useful tool, but that does not mean everyone can use it without any effort.
Users sometimes need to tweak command parameters, and the version upgrade of Appium or dependent platform sometimes causes problems.
As the lead developer of a cloud testing service using Appium as its backend, I have been managing these problems with various measures.
In this session, I introduce especially unique ones of all these measures.
Outline/Structure of the Demonstration
- How we are wrapping Appium to make it more user-friendly (This topic contains code samples)
- Scrolling to the specific element
- Catch-all wait
- Using AI locator effectively
- Picker wheel
- Hiding keyboard
- How we are managing the Appium instability issue
- Reporting issues and submitting pull requests
- Preparing our own regression test set for Appium itself
- Collaborating with Appium committer
- Easy bug report feature
- And so on
Learning Outcome
- Learning how to use Appium more conveniently.
- Learning how to overcome Appium's instability more aggressively.
Target Audience
Mobile Automation Engineers, Test Tool Developers
Prerequisite
Basic knowledge or experience about Appium
schedule Submitted 2 months ago
Recent Activities
- verified_user Program Committee accepted proposal - "How we use Appium as our..." by Nozomi Itoschedule 2 weeks ago
- description Nozomi Ito updated proposal How we use Appium as our...schedule 2 weeks ago
- reply Nozomi Ito replied "Hi Arand. > 1. Can you pl..." on the comment Hi Nozomi, 2 points - Ca...schedule 2 weeks ago
Call for Proposals 22 hours left
Submit before Jan 21 '19 12:00 AM IST
We are looking for deep technical topics related to Appium and testing in general. We are committed to diversity and believe in transparency. Hence, all proposals will be public.
Registered user will be able to comment on your proposal. You are required to reply to those comments to provide clarifications, explain revisions and respond to questions. The program team will look at how well you've responded to comments and updated your proposal to incorporate public suggestions. Ultimately the decision to accept a session resides with the program team.
Your proposal stands the best chance to be selected, if it's unique, fully flushed, ready-to-go. Please ensure you've read:
To encourage early submissions and iterative improvement of proposals, we start accepting proposals as soon as we find them a good fit. Since competition gets tougher with progressing time, it is advisable to avoid waiting until the last minute for proposal submission.
Public Feedback
Hi Nozomi,
2 points -
Thanks
Hi Arand.
> 1. Can you please update the proposal to 45-min?
Updated to 45-min. I also updated the Presentation Type to "Demonstration" since I couldn't choose 45-min for "Experience Report" type.
> 2. Can you please update the title to be more in-tune and relevant to the topic?
What do you think is the best among the following? I'm not sure which one is most appealing and appropriate.
Hi Nozomi,
Can you please share some reference slides and also a short video (or a past video recording) of you speaking?
Also, will this be a talk, or will you also be doing some demos?
Hi Anand.
> slides and videos
Sorry, there is no English slide nor video for this or similar topic. The following are not in English or not related to this topic, but they may be helpful for your understanding a little.
> Also, will this be a talk, or will you also be doing some demos?
I have no plan to include demos.
Thanks for the information.
Another question - is this a 20-min talk? Or a 45-min?
If possible, I prefer 45-min. But 20-min talk is also possible.
If you can include some practical aspects and maybe some demo / explaining (and sharing) some of the code, then this could be a good 45-min talk
Thanks for the good suggestion!
I can share and explain our code and demonstrate it. If this is 45-min talk, there is enough time to do so.