Agent support for automating UI Testing
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
The issue names no files, tests, or entry points, so begin by clarifying whether separate-JVM agent support is in scope and reviewing the existing AssertJ Swing architecture. Define the agent boundary and communication approach before implementation. Done should mean application-level UI tests can run with assertions on the testing JVM and minimal assertion overhead in the application JVM.
Written by the indexing model from the issue text.
Description
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 ?
- Dominant language
- Java
- Stars
- 121
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from assertj/assertj-swing
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
assertj/assertj-swing#279 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
assertj/assertj-swing#278 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
assertj/assertj-swing#276 · 1 comment ·
-
Update unit test to avoid deprecated `ExpectedException.none()` by using `Assert.assertThrows()` Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
assertj/assertj-swing#275 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
assertj/assertj-swing#277 · 1 comment ·
All issues in assertj/assertj-swing
Similar issues
-
certification
Difficulty 1/5 Under an hour Newbie friendliness 80/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
[BUG] ECR GetAuthorizationToken returns a proxyEndpoint for the default region, not the request's Openbug ecr
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Needs: Triage Type: Feature request
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
AntennaPod/AntennaPod#8794 ·
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
github/copilot-sdk#2760 ·