Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Making the tests more easy to run


Pascal,

This is a good idea. The CVS test configurations are already shared in this way.  However, there are a few issues that cause this to be problematic:

1) It is not easy to switch the target platform of a test. This can be circumvented by creating a launch config for each platform but this is not ideal. It would be conceivable for the launcher to have a dropdown that allowed the platform to be selected but currently the platform is encoded in several command line arguments that must each be changed manually.

2) The runtime workspace is encoded in the launch configuration as an absolute path. At some point, there was talk of supporting variables in the launch configuration but I don't think they are supported yet (at least not in the JUnit launcher)

3) Some test cases (e.g. CVS) require additional input (e.g. test repository location). This can be overcome by a standard readme file location for those test plugins that require additional configuration.

If anyone knows of workarounds for any of these, I would be happy to hear them.

Michael



Pascal Rapicault/Ottawa/IBM@IBMCA
Sent by: eclipse-dev-admin@xxxxxxxxxxx

17/01/2005 12:06 PM

Please respond to
eclipse-dev

To
eclipse-dev@xxxxxxxxxxx
cc
Subject
[eclipse-dev] Making the tests more easy to run






Running the whole test suite from a random component should be made more easy.
For that I have a small suggestion:

       - create the appropriate "JUnit plugin test" launch configuration for the whole suite

       - save this configuration in the project that contains the tests (to save the configuration go to the common tab of the launch configuration) and version it.


PaScaL


Back to the top