Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for testing on apps started via WebStart #51

Open
croesch opened this issue Feb 8, 2014 · 1 comment
Open

Support for testing on apps started via WebStart #51

croesch opened this issue Feb 8, 2014 · 1 comment

Comments

@croesch
Copy link
Collaborator

croesch commented Feb 8, 2014

Issue by Michael Hüttermann from Mon, 12 Oct 2009 14:57:02 -0500
Originally opened as http://jira.codehaus.org/browse/FEST-240


It is interesting to test applications which run in different classloader scenarios. One major use case is apps started by WebStart. They behave different than the same apps/test without WebStart. Tests set on top of WebStart would further improve the test quality (more realistic in special cases). This feature can be used in JavaFX scenarios too.


votes (original issue): 0
watches (original issue): 0

@croesch
Copy link
Collaborator Author

croesch commented Feb 8, 2014

Comment by kgeis from Mon, 12 Oct 2009 16:50:18 -0500


I haven't dealt with the classloading issue, but I've tested my WebStart app by creating my own ServiceManagerStub. I wrapped the application with a simple main() that registers the ServiceManagerStub and then calls the app's main() method. I created a BasicService that just logs when a URL is shown. I could also use it like a mock if desired by implementing something like BasicServiceImpl.assertDocumentShown(URL).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant