Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Feature Request: Add support for external activity discovery tools (e.g. activity_finder)

未关闭
#1,230 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
冷清
技术栈
android, python
领域
mobile

调研方向

Issue 中没有确定任何文件、测试或入口点。首先明确目标是 Appium 客户端 API、插件或 hook 接口,还是外部工具集成,然后定义所支持的 Android 行为,以及能够确认完成的测试。

由索引模型根据 Issue 内容生成。

描述

Hi Appium team,

I would like to propose a feature enhancement that may improve Android automation debugging and activity handling.

I have developed a lightweight open-source tool called activity_finder:
https://github.com/jaxonister/activity_finder

Problem

In real-world Appium automation, especially on Android, one common challenge is discovering:

  • current foreground activities
  • available activities in an app
  • activity transitions during testing

This often requires multiple adb commands or manual inspection, which slows down debugging and test development.

Proposal

The tool activity_finder provides a simple way to:

  • list and detect Android activities
  • identify current running activity
  • help quickly locate target activity for automation scripts

It could be useful if Appium could:

  • integrate similar activity discovery capability
  • or provide a plugin / hook interface for external tools
  • or expose a standardized API for activity inspection
Why this matters

Better activity visibility would significantly improve:

  • test stability
  • debugging efficiency
  • onboarding for new automation engineers
Optional integration idea

Even a simple command or extension like:

  • driver.getCurrentActivity()
  • driver.listActivities()

would help bridge this gap.

Conclusion

I believe this feature could improve Android automation workflows in Appium ecosystem, and I would be happy to contribute or discuss implementation ideas further.

Thanks for your time 🙌

主要语言
Python
星标
1.8k
派生
570
平均合并
1 天 10 小时
30 天内合并 PR
24

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

appium/python-client 的其他 Issue

查看 appium/python-client 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。