This document discusses adding new commands in Appium 2.0. It begins by introducing the speaker and their background. It then outlines the topics to be covered: 1) About Appium commands, 2) Commands in a fake driver, 3) Calling commands via curl, 4) Adding commands in a Ruby client. It provides an example of adding commands to a fake driver in Appium and calling them via curl. It demonstrates adding commands to a Ruby client to call endpoints in the fake driver and discuss proper formatting of requests.
This document discusses adding new commands in Appium 2.0. It begins by introducing the speaker and their background. It then outlines the topics to be covered: 1) About Appium commands, 2) Commands in a fake driver, 3) Calling commands via curl, 4) Adding commands in a Ruby client. It provides an example of adding commands to a fake driver in Appium and calling them via curl. It demonstrates adding commands to a Ruby client to call endpoints in the fake driver and discuss proper formatting of requests.
Chrome Devtools Protocol via Selenium/Appium (Japanese)Kazuaki Matsuo
?
This document discusses using the Chrome DevTools Protocol (CDP) via Selenium and Appium to control and inspect Chrome and Android Chrome browsers. It provides examples of executing CDP commands through Selenium for Chrome on desktop and through Appium for Android Chrome. The CDP allows programs to remotely control and inspect browser activity and state.
The talk was about Appium/XCUITest stuff I faced in Appium development, but corresponding to XC(UI)Test x Xcode 11at https://testnight.connpass.com/event/155429/
Uncovering breaking changes behind UI on mobile applicationsKazuaki Matsuo
?
Capturing HTTP requests during automated tests using a proxy server can help uncover breaking changes in the non-UI layers of mobile applications. The author conducted a case study capturing requests over Appium test scenarios for a long-running app with multiple developers. This uncovered issues like logs being incorrectly reused between views. Placing logs in fragments posed problems if those fragments were used across views. Changes like moving to new programming languages could also inadvertently affect log behavior if not implemented carefully.
This document contains information about an individual who is a software engineer in quality. They are involved in open source software projects on GitHub under their username and have contributed to issues on the Appium project. They previously worked as a senior test automation engineer for 5 years developing skills in languages like Ruby, Kotlin, Swift and Python. Their online presence and activities include maintaining a Twitter account, contributing to podcasts and articles on testing topics, attending conferences, and participating in Slack communities.
This document discusses test automation strategies for mobile applications. It begins with an introduction of the presenter, Kazuaki Matsuo. It then covers various aspects to consider when designing test automation, including scope, phase, level, size and type. For each aspect, it provides examples from Cookpad's test automation for their Android and iOS applications in both Japan and globally. It discusses adapting concepts to real products and challenges integrating performance testing. Finally, it lists some common tools used for mobile test automation.
This document provides tips for using the Android Test Support Library 1.0 including IdlingResource for asynchronous tasks, parametrized testing to run the same test with different parameters, GrantPermissionRule to grant permissions in tests, and the Android Test Orchestrator to control test execution order. Additional tips include using AssertJ or Truth for assertions and enabling the Test Orchestrator in Gradle to control test order.
This document provides a 3 sentence biography for Kazuaki Matsuo. Kazuaki Matsuo works as a Software Engineer in Quality and Test at Cookpad Inc. focusing on programming languages and maintaining Appium client libraries. His Twitter handle is @Kazu_cocoa.
1) The document discusses Selenium Committer Day 2017 and Kazuaki Matsuo's involvement in open source software communities as a maintainer of Appium client libraries.
2) It encourages participation in OSS through asking questions, providing answers, giving support, and making contributions to help projects and communities.
3) Small contributions can start with fixing typos or syntax issues and grow into more substantial code changes that support popular OSS like Appium and EarlGrey.
This document discusses testing mobile applications with entire development teams. It describes a meeting called Kakuninkai that the Cookpad iOS team holds to test new features by role-playing as different user types before public release. The goal is to uncover any unexpected behaviors or strange user experiences rather than just checking for broken features. Team members explain new features and are given 5-10 minutes each to test features by taking on personas like "evil users" or "edge case users".
This document discusses tips for reducing flakiness in automated UI tests. It defines flaky tests as tests that can sometimes pass and sometimes fail for the same code. Common causes of flakiness in UI tests are animations and network connections. The document recommends disabling animations through adb commands or APIs to reduce flakiness. It also discusses using EarlGrey to implement similar tips for reducing flakiness on iOS automated UI tests by enabling fast animations.
This document discusses testing practices at Cookpad, a company that develops large web and mobile applications. It outlines their philosophy of prioritizing user experience and keeping development cycles quick through practices like frequent small releases and automated testing. For their web application, which is a large Ruby on Rails monocodebase, it describes their extensive use of RSpec tests as well as tools they developed to help speed up testing. For their mobile applications, it discusses their bi-weekly release process and focus on unit, integration and UI testing using tools like Appium and Espresso. It also acknowledges challenges in moving to microservices and continuous testing of mobile apps.
UI tests have supported re-engineering of the Cookpad iOS app, which has over 35 million users. The app is developed continuously, releasing every 2-4 weeks. UI tests were implemented in 2014 to check external and internal changes as the app is re-written and refactored. Automated UI tests help reduce fear for developers during re-engineering. They also help ensure quality and stability as the mobile environment and services change frequently. UI tests are important for legacy re-engineering projects to enable continuous development.
