![]() |
|
|
|
|
Change By:
|
Robert Šiška
(21/Feb/13 8:56 AM)
|
|
Description:
|
Since the issue MGNLSTK-1073 identified, we decided that we need tests that guarantee the configuration of a migrated module and of a new installation is the same.
What the tests must do:
- run the latest version of the migration on a module
- compare this configuration with a freshly installed module
- the test are ok only if the configuration is the same
The affected modules are: STK, FORM, SHOP, PUR, Commenting.
To run the tests, build with *integration-test* profile:
{{$ mvn install -P integration-test}}
*Details of the tests
*
:
*
_magnolia-migration-tests_ bootstraps old configurations of tested modules and adds servlet
_ComparingServlet_ with mapping */.magnolia/compare*, which compares two node structures.
The _magnolia-migration-tests_ migrates old configurations when the module is installed.
After the instance is ready, the integration tests from
_magnolia-migration-integration_ module are started.
These tests use _ComparingServlet_ to test whether the configurations differ.
The output of _ComparingServlet_ is human readable, so it can help with resolving differences.
{code}
$CONTEXT/.magnolia/compare?path1=/modules/form-OLD&path2=/modules/form&repository=config
{code}
(i) Parameter _repository_ is set to config by default
Possible drawback is, that the version handlers of tested modules need to be duplicated in version handler of _migration-integration-tests_.
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <
[email protected]>
----------------------------------------------------------------
