|
| Re: ideas about plugin automation test [message #461917 is a reply to message #461895] |
Thu, 18 January 2007 10:21  |
 Alex Blewitt
Messages: 946
Registered: July 2009 |
Senior Member |
|
|
I presented an EclipseCon presentation last year on the subject; I believe that murphee is doing a similar for this year. You can do it, but you've got one of two choice; either you have to do all the tests out-of-container (i.e. just run the tests that don't need the workbench up and running) as part of the normal build/test cycle, and then do the in-container ones in a separate phase at the end.
Because the in-container tests need a running workbench, and the running workbench needs both the built plugin and all its dependencies installed, it's really not something that makes sense to fire up the workbench for every test indivudally. As a result, the plugin tests have a single 'test everything' plugin that acts to your build control (e.g. maven) as a single test, but then inside runs all the in-container tests. It'll generate the standard JUnit results, so Maven still sees lots of results, even if it only sees one. Forking each test by starting up a new workbench, whilst it may be the way Maven does it for JUnit tests, is just really not going to work.
I also put a blog post about automatically having in-container and out-of-container tests:
http://alblue.blogspot.com/2006/03/javaeclipse-running-all-t ests-in.html
The EclipseZilla presentation is at:
http://www.rcpapps.org/EclipseCon2006/
Or, if it can't be found there, look for submission 18 on http://eclipsezilla.eclipsecon.org.
Alex.
|
|
|
Powered by
FUDForum. Page generated in 0.02979 seconds
] 
Search
Help
Register
Login
Home
