Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
In the last years we've decided to move integration tests closer to the modules they live in, which is a good thing (TM).
There are also good things about having a central place to execute them, such as the ability to run those tests on multiple Java versions.
One idea of how to approach this is to define integration tests in the modules, and run them during the regular build. On top of that, deploy the integration tests as their own artifacts (maybe same but with integration-test classifier ) and then execute them as part of the Sling ITs.
This would get us the best of both worlds - tests living next to their module, and also the ability to execute "all" tests in a single unit.
Attachments
Issue Links
- mentioned in
-
Page Loading...