test: add Android integration tests for IME engine queries - #1104
Open
Dor-bl wants to merge 1 commit into
Open
Conversation
`GetIMEAvailableEngines` had no test coverage anywhere in the suite. These tests exercise it against the emulator and assert the extracted engine ids are usable strings, plus that the active engine reported by `GetIMEActiveEngine` is one of the available ones. Picked up by the existing `FullyQualifiedName~Android` filter in the functional test workflow, so no CI changes are needed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Km7CV8oXuX8sZAsz9azssA
Contributor
There was a problem hiding this comment.
Pull request overview
Adds Android integration test coverage for the Appium IME (Input Method Editor) APIs, ensuring GetIMEAvailableEngines and GetIMEActiveEngine are exercised against a real/emulated Android environment and validating basic invariants about the returned engine identifiers.
Changes:
- Added a new Android integration test fixture validating
GetIMEAvailableEnginesreturns a non-empty list of non-blank engine IDs. - Added an Android integration test asserting the active IME engine returned by
GetIMEActiveEngineis included in the available engines list. - Added one-time setup/teardown to create and dispose an
AndroidDriversession for these tests.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Dor-bl
added a commit
to Dor-bl/dotnet-client
that referenced
this pull request
Aug 19, 2026
The template only offered "Test fix" for anything test related, so PRs that add coverage for previously untested functionality (e.g. appium#1104) had to be filed under a box describing stability fixes, and it asked whether integration tests were provided for changes that *are* the tests. - add a "New test coverage" type next to "Test fix" - replace the "Integration tests" question with a "Tests" section that distinguishes unit from integration tests, asks how they run, and allows an explained "no automated tests" - add "not applicable" to the documentation checklist - document the conventional-commit title prefixes that labeler.yml and release-drafter derive labels, release notes and semver from - add a "Related issue" line Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Co16HzbYRDPDjUh6zg1r1D
Dor-bl
added a commit
to Dor-bl/dotnet-client
that referenced
this pull request
Aug 19, 2026
The template only offered "Test fix" for anything test related, so PRs that add coverage for previously untested functionality (e.g. appium#1104) had to be filed under a box describing stability fixes, and it asked whether integration tests were provided for changes that *are* the tests. - add a "New test coverage" type next to "Test fix" - replace the "Integration tests" question with a "Tests" section that distinguishes unit from integration tests, asks how they run, and allows an explained "no automated tests" - add "not applicable" to the documentation checklist - document the conventional-commit title prefixes that labeler.yml and release-drafter derive labels, release notes and semver from - add a "Related issue" line Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Co16HzbYRDPDjUh6zg1r1D
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GetIMEAvailableEngineshad no test coverage anywhere in the suite. These tests exercise it against the emulator and assert the extracted engine ids are usable strings, plus that the active engine reported byGetIMEActiveEngineis one of the available ones.Picked up by the existing
FullyQualifiedName~Androidfilter in the functional test workflow, so no CI changes are needed.List of changes
This pull request adds a new integration test class for Android IME (Input Method Editor) functionality. The new tests verify that the driver can correctly retrieve available IME engines and the currently active engine on an Android device.
New Android IME integration tests:
ImeTestclass intest/integration/Android/ImeTest.csto test IME functionality using the Appium Android driver.GetIMEAvailableEnginesreturns a non-empty list of installed IME engines.Types of changes
What types of changes are you proposing/introducing to the .NET client?
Put an
xin the boxes that applyDocumentation
This can be done by navigating to the documentation section on http://appium.io selecting the appropriate command/endpoint and clicking the 'Edit this doc' link to update the C# example
Integration tests
Details
Please provide more details about changes if necessary. You can provide code samples showing how they work and possible use cases if there are new features. Also, you can create gists with pasted C# code samples or put them here using markdown.
About markdown please read Mastering markdown and Writing on GitHub