It appears that this fat jar contains the compile-time dependencies of the test artifacts.
It actually contains all the dependencies. In Maven parlance compile gets included in the runtime as well.
The run-time dependencies of tests may be different from the compile-time dependencies.
Are you talking about dependencies that are somehow not expressed in the tests-artifact's pom files? I believe it would be extremely useful if we can also manage them via poms. Can you please give me a few examples?
Aside from this, there may well be a whole host of parameters you need to pass in to your test as system properties.
Yes. And that will be addressed in future JIRAs.
Now, of course if the current set of test-execution pom files is still useful to some in the Bigtop community there's no need to remove that code. My intent here is to be able to have a single artifact with a really simple CLI interface that I can use to run tests. My ideal state is something that would let me do this:
$ java -jar fat.jar
$ java -jar fat.jar -list
// lists all the tests and suites
$ java -jar fat.jar -info Test
// prints required fixtures
$ java -jar fat.jar -run Test
// runs the tests