[jira] [Updated] (SLING-11778) Test that the feature models generated by the CPConverter are deployable
[ https://issues.apache.org/jira/browse/SLING-11778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-11778: Fix Version/s: Content-Package to Feature Model Converter 1.3.8 (was: Content-Package to Feature Model Converter 1.3.6) > Test that the feature models generated by the CPConverter are deployable > > > Key: SLING-11778 > URL: https://issues.apache.org/jira/browse/SLING-11778 > Project: Sling > Issue Type: Improvement > Components: Content-Package to Feature Model Converter >Reporter: Robert Munteanu >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.3.8 > > > 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. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-11778) Test that the feature models generated by the CPConverter are deployable
[ https://issues.apache.org/jira/browse/SLING-11778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-11778: Fix Version/s: Content-Package to Feature Model Converter 1.3.6 (was: Content-Package to Feature Model Converter 1.3.4) > Test that the feature models generated by the CPConverter are deployable > > > Key: SLING-11778 > URL: https://issues.apache.org/jira/browse/SLING-11778 > Project: Sling > Issue Type: Improvement > Components: Content-Package to Feature Model Converter >Reporter: Robert Munteanu >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.3.6 > > > 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. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-11778) Test that the feature models generated by the CPConverter are deployable
[ https://issues.apache.org/jira/browse/SLING-11778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-11778: Fix Version/s: Content-Package to Feature Model Converter 1.3.4 (was: Content-Package to Feature Model Converter 1.3.2) > Test that the feature models generated by the CPConverter are deployable > > > Key: SLING-11778 > URL: https://issues.apache.org/jira/browse/SLING-11778 > Project: Sling > Issue Type: Improvement > Components: Content-Package to Feature Model Converter >Reporter: Robert Munteanu >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.3.4 > > > 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. -- This message was sent by Atlassian Jira (v8.20.10#820010)
