bndtools
Better documentation for `tester.testnames `
The documentation says:
scan all running bundles for any bundles with the Test-Cases header set, or with any classes matching the -tester.testnames property;
Unfortunately, it does not say whether the property can be used with wildcards. For example, I would like to have separate executions of the testing plugin that mimic surefire and failsafe in Maven, i.e. running the first with something like -tester.testnames=*Test and the second with -tester.testnames=*IT.
It would also be nice if the documentation said how to specify multiple values and how to possibly escape them in a .bndrun file since , is used there as a property separator.
This is a valid point. In case I don't get to fixing the documentation soon, the answers are:
- There is no wildcard support in
tester.names. You can only match by exact name. - You can specify multiple class/method selectors separating them with a comma, and then quoting the entire selector string, eg: tester.names='my.clazz.One:method2,my.clazz.Two,my.pkg.Three.method1'
- Matching parameterized tests is tricky. When I figure out how to do it properly, I'll document that too. :smile:
