How to use many workspaces to many JUnit Plug-in Tests?

[Eugeniy_N]

How to use many workspaces to many JUnit Plug-in Tests?

Clear workspace data not always approaches. Use of "Variables..." in "Open Run Dialog..." - not absolutely convenient decision. Tests at use of Window Tester can be much (100, 200, 500 and more). How to be?

[Phil Quitslund]

Could you elaborate a bit on your problem? Each windowtester test run will be associated with one workspace. If you want to run a group of tests for one WS and another group of tests for another WS these will have to be different suites run via different launch configurations. What am I missing? How is this inconvenient?

[Eugeniy_N]

Could you elaborate a bit on your problem? Each windowtester test run will be associated with one workspace. If you want to run a group of tests for one WS and another group of tests for another WS these will have to be different suites run via different launch configurations. What am I missing? How is this inconvenient?

Thanks.

Specification such. We shall admit is available:
1) 300 usual tests. They use 1 workspace with clearing this 1 workspace.
2) 400 special tests. They use 400 workspaces without their clearing.

At changes of a site of 400 workspaces - it is inconvenient to change them through options of "Open Run Dialog...". If it were variables in a code, it would be convenient to make operations of search/replacement.

Will agree, that in such here a kind it would be very convenient to support structures of folders of workspaces:

Code: Select all

public static final String SLASH = "\\";
private static final String FOLDER_TESTS = "D:"+SLASH+"tests";
private static final String FOLDER_GUI = FOLDER_TESTS+SLASH+"gui";
...
...
...

[Phil Quitslund]

Thanks for the elaboration.

The issue is ultimately with the Eclipse JUnit PDE test runner. Essentially, WindowTester (WT) tests are *just* JUnit tests and are run using the standard Eclipse JUnit test runner. The end result is that configuring the environment, like the workspace location, is all taken care of by Eclipse before the WT runtime bootstraps. It would be interesting to see if the Eclipse runner could be used to satisfy your requirements... I'm frankly not sure! Your best bet might be to post this question to an Eclipse newsgroup. In the meantime, we'll poke around a bit on our end.

Let us know what you discover. Thanks!