[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[tracecompass-dev] Moving the test traces to a separate project
|
Hi all,
I've struggled with adding a new test trace recently (for the debug-info
unit tests), and realized that the process is very cumbersome. Basically
one has to:
- Manually copy the trace to the archive.eclipse.org directory
- Add the trace in about 5 locations in the get-traces.xml script
- Add it to the deletion command in the pom.xml
- Add it to the gitignore
- Expose it in the CtfTestTrace and CtfTmfTestTraces files
It's also quite messy, some are compressed with tar.bz2, others with
zip, which don't require the same Ant commands. Some traces are not
named the same as the archive they are in. Some archives contain more
than one trace. There is also no easy way of just downloading the test
traces without running the tests.
I came to the realization we could instead ship the test traces as a
separate project, a standalone Maven artifact. The test traces would be
put in a jar, which also does compression. We could then use the concept
of Java resources to access them. This will, after all, allow using
FileLocator from within the Eclipse code!
This will also allow removing all the assumeTrue(trace.exists()) calls
we do now, since if the plugin is there the trace will necessarily be
present.
I've done some initial prototyping and the dependency resolution seems
to work well. Next I'll make sure the tests still actually pass...
Any thoughts before I continue moving forward with this?
Cheers,
Alexandre