At this workshop, you'll learn about advanced concepts in Appium. We will learn how to write a single script for Android, iOS and mobile web apps. Once our tests are established, we will work on framework design and report. We will also have a detailed look at how can we automate various mobile gestures using TouchActions and mobile endpoints in Appium and running distributed tests in parallel on various emulators and simulators.
Outline/Structure of the Workshop
- Appium Architecture
- Locating elements using Inspector
- Platform-wise Desired Capabilities
- Start Appium Server programmatically
- Deeper understanding about Gestures
- Run through various gestures like Swipe, LongPress, Double tap, Drag and Drop using TouchActions API
- Explore mobile: endpoints for same gestures on both Android and iOS
- Create our own complex gestures using above endpoints
- Framework Design
- Mobile specific page object annotations
- Write one script to test all platforms
- Chaining of various elements
- Run single tests on Android, iOS and mobile web apps
- Parallelize Tests
- Understanding Appium Server Session
- Desired Capabilities changes required to run tests in parallel
- Run test in parallel on emulators and simulators
- Running tests on Sauce Cloud (if time permits)
- Attendees will come away with knowledge of how to automate Android native apps with Appium.
- Getting started with setting up an Android mobile device grid.
- Running tests single threaded, in parallel, and distributed.
- Also capturing critical report data (logs, screenshots, and video), and
- Running mobile tests on a cloud test service.
QA, Automation Testers, Dev Engineers
Prerequisites for Attendees
- It is mandatory to refresh your basic Appium skills as it is intermediate to advanced Appium workshop
- Detailed setup instructions will be shared couple of weeks before workshop day
- Configure your laptops well before the workshop day
schedule Submitted 10 months ago
People who liked this proposal, also liked:
Abhijeet Vaikar - End-end test code as a first class citizenAbhijeet VaikarSenior Software Engineer (Test)Carousell
schedule 11 months agoSold Out!
"All tests in today's automated regression run have been marked as Untested. What happened?"
"No notifications are being sent for test runs on the channel"
"I pulled latest code, and the framework dependency shows compilation error"
"What does this new method in the framework do?"
How often do you hear such things within your team?
As Quality champions, we need to walk the talk. When we expect our developers to write quality code, write unit tests, build features without introducing bugs, the onus lies on us (as test engineers) to do the same. With almost every test engineering team writing automated tests to check functionality of their products and services, it becomes very important to ensure that the test automation framework and the test scripts are bug-free and follow good standards of software engineering.
It cannot be stressed enough that test automation code should be as good as production code. In order to build production-quality test automation framework and scripts, a number of steps can be taken at:
1. Code & System Level
2. Process & People Level
Our test engineering team went through a transition from having random & unexpected failing test runs to having greater confidence in the quality of the tests. Learn from this case study of our journey to ensure that end-end UI automated tests are built with quality in mind. We will also see demonstration of some of the use cases.
Srinivasan Sekar / Sai Krishna - Testing And Observability in an Integrated Microservices environmentSrinivasan SekarLead ConsultantThoughtWorksSai KrishnaLead ConsultantThoughtWorks
schedule 10 months agoSold Out!
Leading-edge applications are dynamic and adaptive in capabilities that require people to use increasingly dexterous tools and supporting infrastructure, including microservices. All of these applications leverage data in new ways. Decoration and tagging of data with intelligent meta-data have become more important than data itself. To keep up with evolving needs, enterprise devs across industries are shifting from traditional app architectures in favor of more fluid architecture for building data-centric applications.
Microservices break traditionally structured applications into manageable pieces that can be developed and maintained independently. microservices are often decoupled, allowing for updates with little to no downtime, as the other components can continue running.
Moving to distributed Microservices ecosystem brings its own challenges; Among them is the loss of visibility into the system, and the complex interactions now occurring between services. Monitoring these applications only reports the health of it but Observability provides granular insights about the behavior of the system along with rich content. In this talk, we will cover the difference of Monitoring and Observability, data path engineering challenges, pillars of observability, distributed tracing of various microservices, testing in distributed microservices ecosystem, automated observability, etc.