Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
We have a set of tests in the CPConverter that validate what the output looks like. I have a feeling that we would be better off if we would validate that the feature models and associated artifacts can actually be installed.
We can do this by setting up a Sling application that contains the prerequisites ( Oak/FileVault mostly ) and starting that application with the feature models generated. The application can be parameterised to use different FileVault versions, so we are certain that we don't run into problems like SLING-11777 .
We can then validate that
- all bundles are started
- all content packages are installed
I think this would cover a gap that we have regarding validating the correctness of the artifacts that we generate with the CPConverter.
We don't have to start with a lot of tests, but having 1-3 content packages with good coverages validated as "installable" would IMO be a great step forward.