That would correspond to my proposed solution 4, which requires to
create about 70 new fragments and splitting up the >4500 existing unit
tests.
Nevertheless, this approach would not work to test a fragment itself, since a fragment cannot be a fragment of a fragment.
Am 28.11.2013 09:31, schrieb Sievers, Jan:
Nevertheless, this approach would not work to test a fragment itself, since a fragment cannot be a fragment of a fragment.
Paolo
Am 28.11.2013 09:31, schrieb Sievers, Jan:
1) Converting the plain-java test project into a plugin test project Disadvantages:
- In order to be able to test classes in internal packages, I have to export every single package with x-friend:<my.test.plugin> notation and have to repeat this procedure for each new tested packageHave you tried using test fragments instead?
Jan _______________________________________________ tycho-user mailing list tycho-user@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/tycho-user
