# Can LLM Agents Learn to Test? Maintaining Scoped Experience as Testing Evidence for Mobile GUI Testing

DevFeed: [Can LLM Agents Learn to Test? Maintaining Scoped Experience as Testing Evidence for Mobile GUI Testing](<https://devfeed.tech/articles/can-llm-agents-learn-to-test-maintaining-scoped-experience-as-testing-evidence-for-mobile-gui-testing-118061.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.05873>)

Author: Zimu Liu, Xiaoxi Guo, Xiaolu Tang, Liang Yu

Published: 2026-11-05T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Mobile Testing](<https://devfeed.tech/topics/mobile-testing.md>), [computer-use](<https://devfeed.tech/topics/computer-use.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Retrieval Augmented Generation (RAG)](<https://devfeed.tech/topics/retrieval-augmented-generation-rag.md>)

Tags: [advice](<https://devfeed.tech/tags/advice.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-control](<https://devfeed.tech/tags/agent-control.md>), [agents](<https://devfeed.tech/tags/agents.md>), [android](<https://devfeed.tech/tags/android.md>), [app](<https://devfeed.tech/tags/app.md>), [bounded](<https://devfeed.tech/tags/bounded.md>), [case-study](<https://devfeed.tech/tags/case-study.md>), [changes](<https://devfeed.tech/tags/changes.md>), [comparisons](<https://devfeed.tech/tags/comparisons.md>), [context](<https://devfeed.tech/tags/context.md>), [control](<https://devfeed.tech/tags/control.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [experience](<https://devfeed.tech/tags/experience.md>), [gui](<https://devfeed.tech/tags/gui.md>), [learn](<https://devfeed.tech/tags/learn.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llm-agents](<https://devfeed.tech/tags/llm-agents.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [test](<https://devfeed.tech/tags/test.md>), [testing](<https://devfeed.tech/tags/testing.md>)

## AI overview

AdaptiTest proposes maintaining reusable mobile GUI testing experience with explicit applicability scopes and trace provenance, plus confirmation, revalidation, and withdrawal. A Reflector role controls persistence; recalled entries are advice, and the approach changes retrieved context rather than model weights. In a read-only Android evaluation, a six-task, three-repeat subset completed 18/18 runs with memory versus 3/18 without it, though a grounded single-agent control also solved the earlier hard-task slice. The excerpt also reports 13 selected UI-update hazard records across nine subjects. A separate cross-session probe is excluded from efficacy conclusions, and archived implementation evidence does not establish enforcement of every mechanism. The results are a bounded case study, not evidence of general efficacy, superiority over independent GUI agents, or unrestricted exploration.

## Source excerpt

arXiv:2611.05873v1 Announce Type: new Abstract: Repeated mobile GUI tests can reuse routes, locators, and recovery strategies from earlier executions. However, a route that worked in one workflow or app version may be irrelevant or misleading in another. We study how an LLM-based tester can retain useful experience while withholding entries contradicted by current observations. We present a maintenance contract for AdaptiTest in which reusable experience has an explicit applicability scope, trace provenance, and a lifecycle for confirmation, revalidation, and withdrawal. The contract reserves persistence for a Reflector role and treats recalled experience as advice. The archived implementation does not establish end-to-end enforcement of every specified mechanism. The design changes retrieved context, not model weights. The evaluation uses read-only Android workflows and archived internal comparisons. A six-task, three-repeat ready subset reports 18/18 completed runs with memory versus 3/18 without it, but a grounded single-agent control also solves the earlier hard-task slice. A separate cross-session probe is excluded from efficacy conclusions because of confounded route schedules and unvalidated state labels. We examine 13 selected real-update hazard records across nine subjects, distinguishing stale-locator observations from policy-based withholding and offline retrieval diagnostics. The latter do not measure live-device failures or actions saved. These events are UI changes, not confirmed regression bugs. The evidence supports a bounded design and case study; it does not establish general efficacy, superiority over independent GUI-agent systems, or unrestricted exploration.