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 ?

Das Issue nennt keine Dateien, Tests oder Einstiegspunkte. Beginne daher damit zu klären, ob die Unterstützung für Agents in einer separaten JVM im Umfang enthalten ist, und überprüfe die bestehende AssertJ Swing-Architektur. Lege vor der Implementierung die Agentengrenze und den Kommunikationsansatz fest. Als abgeschlossen sollte gelten, dass UI-Tests auf Anwendungsebene mit Assertions auf der Test-JVM und minimalem Assertion-Overhead in der Anwendungs-JVM ausgeführt werden können.

Vom Indexierungsmodell aus dem Issue-Text verfasst.