[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipse-dev] Making the tests more easy to run
|
>If anyone knows of workarounds for any of these, I would be happy to hear
them.
In an ongoing effort to make Michael happy :-),
Item 1 is no longer an issue (as of 3.1M4), the -os, -ws, -arch are no
longer hardcoded in the launch configuration itself.
If you have old launch configs in which they are hardcoded, you could
safely remove them from the program args field.
Upon launching, PDE implicitly appends these args to the command line
depending on the environment where you are launching your tests.
So the same launch configuration can be used on all platforms.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=72156
Regarding item 2:
PDE passes the workspace directory as-is to the runtime in the "-data"
argument.
So if you enter a relative path, I see no reason why it should not work.
You are right however in that we don't support variable substitutions in
the launch configuration.
Wassim.
Michael
Valenta/Ottawa/IB
M@IBMCA To
Sent by: eclipse-dev@xxxxxxxxxxx
eclipse-dev-admin cc
@eclipse.org
Subject
Re: [eclipse-dev] Making the tests
01/17/2005 01:20 more easy to run
PM
Please respond to
eclipse-dev
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: To
eclipse-dev-admin@xxxxxxxxxxx eclipse-dev@xxxxxxxxxxx
cc
17/01/2005 12:06 PM Subject
[eclipse-dev] Making the
tests more easy to run
Please respond to
eclipse-dev
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
