fix: appium touch perform by kobenguyent · Pull Request #5035

fix: appium touch perform by kobenguyent · Pull Request #5035 · codeceptjs/CodeceptJS

Pull Request Overview

This PR refactors the Appium helper to use W3C actions for touch interactions, updates the corresponding documentation and tests, and standardizes CI workflow YAML quoting and triggers.

Refactored touchPerform helper method to call browser.performActions and updated JSDoc/examples.
Tagged the touch-perform integration test with @quick.
Converted Appium docs to single-quote syntax, removed semicolons, and realigned example blocks.
Standardized quoting in CI workflows and adjusted the Appium Android workflow trigger.

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
test/helper/Appium_test.js	Added `@quick` tag to the touchPerform test title
lib/helper/Appium.js	Switched `touchPerform` from `touchPerform` to `performActions`
docs/helpers/Appium.md	Updated touchPerform docs, code examples switched to single quotes
docs/plugins.md	Removed stray list marker
.github/workflows/check.yml	Standardized YAML quoting
.github/workflows/appium_Android.yml	Broadened branch trigger

Comments suppressed due to low confidence (4)

.github/workflows/appium_Android.yml:7

Using the wildcard '**' in branch triggers will run this workflow on every branch. Consider narrowing it to intended branches to reduce unnecessary CI runs.

test/helper/Appium_test.js:330

Verify that the test suite is configured to recognize the @quick tag; otherwise this annotation may be ignored by the runner.

    it('should react on touchPerform action @quick', async () => {

docs/helpers/Appium.md:760

[nitpick] The markdown list structure in this section has inconsistent indentation and markers after the bulk update. Align nested bullets and code fences to improve readability.

Performs a specific touch action using W3C actions.

lib/helper/Appium.js:1375

After calling performActions, consider invoking releaseActions() or clearActions() on the browser to reset the input state and avoid residual pointer sessions.

    return this.browser.performActions(actions)