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

Agent support for automating UI Testing

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
java
领域
desktop, testing

调研方向

该 issue 没有指定文件、测试或入口点,因此应先明确是否将独立 JVM agent 支持纳入范围,并审查现有的 AssertJ Swing 架构。在实现之前定义 agent 边界和通信方式。完成的标准应是:应用级 UI 测试可以在 testing JVM 上执行 assertions,同时在 application JVM 中仅产生最小的 assertion 开销。

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

描述

The support assertJ-swing is great. When trying to use the library to automate some application level tests like running the application and run tests against it, I found the few problems.

  • When we run lot of tests, the objects that are created for assertions and component lookup adds an overhead into the Application Under Testing.
  • Running tests together with the application adds test framework overhead into the Application as well.

We could overcome these problems, if we keep test execution and assertions on the testing jvm and application on its own jvm. To do that we would need a small agent which could perform low level operations that are required by the assertion library and return the results to the testing jvm. This will make sure the testing and assertion has minimal impact on the application jvm.

Do you think this is a good idea to implement ? or the scope of this library is just to test components only ?

主要语言
Java
星标
121
派生
52
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

assertj/assertj-swing 的其他 Issue

查看 assertj/assertj-swing 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

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