Agent support for automating UI Testing

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 ?

El issue no especifica archivos, tests ni puntos de entrada, así que comienza aclarando si la compatibilidad con agentes en una JVM separada forma parte del alcance y revisando la arquitectura existente de AssertJ Swing. Define los límites del agente y el enfoque de comunicación antes de la implementación. El trabajo debería considerarse terminado cuando los tests de UI a nivel de aplicación puedan ejecutarse con assertions en la JVM de testing y un overhead mínimo de assertions en la JVM de la aplicación.

Escrito por el modelo de indexación a partir del texto del issue.