appium / appium/java-client

Commands interface in v9 missing command name/info & args

Open
#2,219 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
1.3k
Forks
752
Avg merge
6d 21h
Merged PRs (30d)
8

Description

Description

In previous versions of Appium, I've been able to collect timings of executed commands. After update to v9, the commands interface no longer contains the name of the executed command (nor any other information to use in filtering).

Environment

  • Java client build version or git revision if you use some snapshot: 9.3.0
  • Appium server version or git revision if you use some snapshot: 2.11.2
  • Desktop OS/version used to run Appium if necessary: macOS
  • Node.js version (unless using Appium.app|exe) or Appium CLI or Appium.app|exe: v22.4.1
  • Mobile platform/version under test: iOS
  • Real device or emulator/simulator: simulator

Details

Please provide more details, if necessary.
The code that worked previously:

driver.activateApp(app.name)

// or following, the result is the same:
// driver.executeScript("mobile:launchApp", ImmutableMap.of("bundleId", app.name));

driver.events.commands.filter { it.name == "activateApp" }

Currently, the commands interface doesn't have any useful identifier for commands triggered by drivers:

"commands": [
    {
      "cmd": "getLogEvents",
      "startTime": 1723451304905,
      "endTime": 1723451304905
    },
    {
      "cmd": "execute",
      "startTime": 1723451304936,
      "endTime": 1723451312314
    }
  ],

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Java client's driver.events.commands interface and compare its v8 and v9 behavior, using activateApp and executeScript("mobile:launchApp") as the reported cases. Check how the commands output is populated; done means driver.events.commands exposes a useful command identifier and information for filtering, with coverage for these cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, java
Domain
mobile-dev, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.