How do I record a mobile test without writing Appium code?
In a SmartestQA MOBILE project you click Record Actions, which opens the Appium Inspector on the live screen of your device, switch Record on and tap the elements. Save Steps stores each one as an action with its locators, and the step types and Global actions in Automate cover gestures, keys, the app lifecycle and assertions, so you write no Appium code.
In short
On this page you can
- Record an Android or iOS screen by tapping it, with no script.
- Save each element as an action with its locators, best first.
- Add gestures, keys and app steps from Global Actions without capturing an element.
- Read a value from the screen and reuse it in a later step.
- Try the test with a Dry Run on a local device or a Device Farm device.
How to use it
- Start the agent and Appium Server on the computer next to the device; the Local Emulator Setup tab lists the steps.
- In the MOBILE project click Record Actions.
- Fill Configure Mobile Device and pick This computer or Device Farm.
- Switch Record on and tap the elements on the live screen.
- Name the page and click Save Steps.
The short answer#
You record by tapping. In a MOBILE project, Record Actions opens the Appium Inspector inside SmartestQA. It shows the live screen of your phone, emulator or Device Farm device. With Record on, each element you tap is added to the list, and Save Steps stores them as actions with their locators, an element screenshot and the element’s bounds. In a test case you put those actions in order and add ready-made steps for swipes, keys, waits and assertions. You write no Appium code.
Appium itself still has to run, because it is the bridge between SmartestQA and the device. For a device on your own computer you need the SmartestQA agent online and Appium Server on port 4723; one line in a terminal installs and starts it.
The problem this solves#
Many teams test their mobile app by hand, because automating it means writing Appium code: start a session, find each element by a locator, wait for it, deal with the keyboard. That needs someone who programs, and often there is one such person on the team. The testers who know the app best cannot add a test themselves, so new tests wait in a queue.
Hand-written scripts also keep their locators in the code. When a screen changes, someone has to find the right line. What is missing is a way to capture a screen by using it, keep each element as a reusable item with its locators, and add swipes, keys and checks as ready-made steps.
An example#
This is an illustration, not a customer story. A tester on a team with an Android hotel booking app wants a test for the search screen, and nobody on the team writes Appium code.
- The tester follows the Local Emulator Setup tab: an emulator, the single line that installs and starts Appium, then the agent. Under Connected Devices the emulator shows a green Appium chip.
- In Mobile Config, Read APK fills App Package and App Activity. After Save Configuration the message is “Mobile configuration saved successfully”.
- The tester clicks Record Actions, fills Configure Mobile Device and picks This computer. With Record on, the tester taps five elements on the live screen: the city field, two date fields, the guest counter and the search button.
- The tester names the page
Searchand clicks Save Steps. The window says “5 actions will be created”, then “5 actions saved successfully.” - In the test case the tester picks the saved actions from the Action List, adds Hide Keyboard from Global Actions with Add to step list, and adds an Assert Text step with the expected title of the result list.
- A Dry Run with Dry Run (local) runs the test on the emulator.
The test exists without a line of Appium code, and the five elements are saved actions that the next test case can pick from the Action List.
By hand, with hand-written Appium scripts, and with SmartestQA#
| Question | Testing by hand | Hand-written Appium scripts | SmartestQA |
|---|---|---|---|
| Who can create a test? | Any tester | Someone who writes code | Someone who can use the app: you tap elements in the Appium Inspector and save them as actions |
| Do I still need Appium? | No | Yes, and you set up the server and the session yourself | Yes, for a device on your own computer: Appium Server on port 4723. The Local Emulator Setup tab gives one line that installs and starts it |
| Where do the locators come from? | None are needed | You inspect the screen and write them into the code | The recorder saves three per element: a resource-id XPath (95), accessibility_id (90) and the full XPath (80) |
| How do I add a swipe, a Back press or a check? | You do it on the phone | A few lines of code each | Step types such as Swipe and Assert Text, and Global Actions that need no element |
| What happens when a screen changes? | The tester adapts on the spot | Someone updates the locators in the code | Mobile steps are not auto-healed, so keep locators stable: accessibility id and resource-id |
Steps#
Prepare the computer next to the device
In a MOBILE project open Device FarmTest Agents and follow the Local Emulator Setup tab: Android Studio, an emulator,
adb devices, then the single line that installs Appium and the Android driver and starts the server. Start the agent from the Download Client tab with its API key. A real Android phone works the same way: connect it by USB with USB debugging on. See Android emulator on your computer.The agent’s dot turns green and
adb deviceslists the device asdevice, notoffline.Check that SmartestQA sees the device
Under your online Localhost agent, Connected Devices lists the device under Real Devices or Emulators / Simulators. The chip is a green Appium when the server answers and a red Appium off when it does not. See Connected Devices.
Tell the project which app to open
Open ConfigurationProject PanelMobile Config. For Android, Read APK reads an
.apkfile of up to 200 MB and fills App Package and App Activity. For iOS, Read IPA fills Bundle ID (Optional). Click Save Configuration. See Local device.“Mobile configuration saved successfully”.
Open the inspector
In the MOBILE project click Record Actions (tooltip “Open Appium Inspector”).
Configure the device
In Configure Mobile Device the platform is fixed by the project. Fill Device Name, App Package and App Activity (Android) or Bundle ID (iOS), optionally App Path, and pick the source: This computer or Device Farm.
Record the screen
Switch Record on and tap elements on the live screen; each one is added. Use the All Actions and Steps tabs to check the list.
Save
Give the page a name and click Save Steps. Without a page name, the platform name is used. See Discover › Mobile.
The window says “n actions will be created”, then “n actions saved successfully.”
Build the test case and try it
In a mobile test case the record slot opens the same inspector: tap an element, choose the action type, use Add Test Step, and Save Steps adds the steps to the test case. Saved actions are also in the Action List, and Global adds steps that need no element. Then start a Dry Run with Dry Run (local) or Device Farm.
Mobile steps you get without code#
These step types exist in MOBILE projects (Android and iOS). Each one is a row in the step list with a chip, not a line of script.
| Group | Step types | Value you fill |
|---|---|---|
| Touch and gestures | Tap, Double Tap, Long Press, Swipe, Scroll, Tap First List Item, Pinch, Drag & Drop | A direction (up, down, left, right) for Swipe and Scroll, an index for Tap First List Item, a scale for Pinch (default 0.5) |
| Input and keys | Type Text, Clear, Clear & Type, Hide Keyboard, Press Key | The text, or an Android keycode (66) or key name (ENTER) |
| App lifecycle | Launch App, Close App, Reset App, Background App, Activate App, Install App, Remove App | Seconds for Background App, the app file for Install App |
| Navigation | Press Back, Press Home, Switch Context, Open Notifications, Open Deep Link | The context, or the URL, for example myapp://orders/1042 |
| Read values | Get Text, Get Attribute, Store Variable | The variable name; later steps pick it with Insert step variable |
| Waits and assertions | Wait For Element, Wait For Text, Wait For Visible, Assert Visible, Assert Not Visible, Assert Text | The expected text |
Shared step types work in mobile projects too: Assertion, Python, API, Database, Mail, Kafka, Global parameter, Wait (seconds) and AI. The full list is in Mobile steps.
Locators the recorder saves#
| Locator | Score |
|---|---|
A resource-id XPath | 95 |
accessibility_id | 90 |
| The full XPath | 80 |
The two top scores swap when accessibility ID is the chosen strategy. How the score is shown: Saved locators.
What you get#
- Actions instead of scripts. Each tapped element becomes a saved action with its locators, an element screenshot and its bounds. You pick saved actions from the Action List.
- Three locators per element, ranked. A
resource-idXPath (95),accessibility_id(90) and the full XPath (80). - Ready-made steps. Global Actions holds pre-built mobile steps, the same in every mobile project: Hide Keyboard, Scroll, Swipe, Tap List Item, Press Back, Press Home, Open Notifications, Press Enter, Launch App, Close App, Reset App and Background App 5s.
- Values that travel between steps. Get Text, Get Attribute and Store Variable save a variable, and the value field of later steps offers Insert step variable.
- Plain logs. A failed assertion logs, for example,
The text of "Total" did not match the expected value "€ 12.00" (found: "€ 10.00"); a wait that runs out logs"Login" did not appear in time. - The same test on other devices. A Dry Run runs on a local device or emulator through your agent, or on a Device Farm device. A pipeline picks its own devices on its Mobile Settings tab.
- A clear time budget. Each step has the project’s Wait Timeout plus 10 seconds; an AI step gets 35 seconds more.
Questions and answers#
Do I need to write Appium scripts or know a programming language?Customers
No. In SmartestQA you tap elements in the Appium Inspector and save them as actions, then build the test from step types such as Tap, Type Text and Assert Text. A Python step exists as a shared step type, but nothing in the recording needs it. See How mobile steps are created.
Do I still have to install Appium?Customers
For a device on your own computer, yes: Appium Server is the bridge between SmartestQA and the device and must run on port 4723. The Local Emulator Setup guide gives one line that installs Appium and the Android driver and starts the server. It needs a current LTS version of Node.js. See Android emulator on your computer.
Does it work for iOS apps?Customers
Yes. The mobile step types exist for Android and iOS, and for iOS the inspector takes a Bundle ID instead of a package and activity. iOS devices and simulators need the agent on a Mac. In Mobile Config, Connected Device lists the simulators and USB devices your agent found. See iOS Configuration.
Can I record on a real phone instead of an emulator?Customers
Yes. Connect the Android phone by USB with USB debugging on. Once adb devices lists it as device, SmartestQA shows it under Real Devices in Connected Devices. See Connected Devices.
Can I record on a Device Farm device?Customers
Yes. In Configure Mobile Device the source is either This computer or Device Farm. Device Farm devices need the Device Farm right on your company’s licence. See Devices.
Which operating system does my computer need?Customers
The SmartestQA agent runs on Windows, macOS or Linux for Android, and the Android emulator guide works on all three. iOS devices and simulators need a Mac. See Download Client.
What happens if a locator matches several elements?Customers
At run time the first matching element is tapped. The inspector warns about this when you capture, so you can pick a more specific element or locator. See At run time.
Are recorded mobile steps repaired when the app changes?Customers
No. Mobile steps are not auto-healed in SmartestQA, so keep locators stable: accessibility id and resource-id. See Project types and engines.
Why does the inspector tell me to make sure Appium Server is running?Customers
Appium runs in the foreground of the terminal that started it. If that terminal was closed, the server is gone and Connected Devices shows Appium off. Run appium in a new terminal and leave it open. See the fix.
Can I add a swipe or a Back press without capturing an element?Customers
Yes. Global on the step toolbar opens Global Actions. Search with “Search action…” and click Add to step list. In the step list these steps show an orange chip with a bolt icon. See Global actions.
Read more#
- Discover › Mobile & desktop: the recorder for mobile and desktop apps.
- Local device setup: emulator, Appium and Connected Devices, step by step.
- Test Agents: download the client, the API key, Online and Offline.
- Mobile steps: every step type with its chip and value.
- Mobile Config: the app and where it runs.
- Connect mobile and desktop apps: the first steps for a phone on your desk.
- How do I build, run and schedule a regression suite?: put the recorded tests in a pipeline.
Didn’t find your answer?Write to support with your project name and what you see on screen.
info@smartestqa.ai