Remove dataprovider in \Combodo\iTop\Test\UnitTest\Integration\iTopModulesPhpVersionIntegrationTest::testITopModulesPhpVersion
The dataprovider was slow, and was very fragile because it contained much PHP code : as seen in 2221e05 when an error appears here it is very difficult to trace :/
So now we have a traditional PHPUnit test method, and still we are testing everytime all modules (not stopping on the first error : we have only one assert at the end instead of an assert per module), and also we're getting the list of modules having errors at the end
The AllowAllData attribute wasn't updated in the nested queries.
It is now set both when calling DBObjectSearch::AllowAllData and when creating a new nested query (\DBObjectSearch::AddConditionExpression)
- N°3053 - Check XML conversion methods
- N°3059 - Automatically set the documentation URLs
- N°3052 - Check community modules XML version against latest version
- N°3054 - Check community modules version against major version
- N°3062 - setup.css file integrity test
- N°3060 - Check consistency between the list of modules and installation.xml
- N°3061 - Automatically check the installation.xml consistency
- N°3268 Add test to check dictionary files: make sure that the Dict::Add declarations match the file name
- New module itop-bridge-cmdb-ticket to cope with the need to install only the CMDB or/and ticketing
- New module itop-structure to hold declarations required by iTop independently from ITIL. Note that these declarations should ideally be moved to application/datamodel.application.xml or core/datamodel.core.xml. Anyhow, the compiler suffers a few limitations and it has been decided to create this module as a workaround.
- Split of known-error module into itop-faq-light and itop-knownerror-light
- New module itop-bridge-cmdb-ticket to cope with the need to install only the CMDB or/and ticketing
- New module itop-structure to hold declarations required by iTop independently from ITIL. Note that these declarations should ideally be moved to application/datamodel.application.xml or core/datamodel.core.xml. Anyhow, the compiler suffers a few limitations and it has been decided to create this module as a workaround.
- Split of known-error module into itop-faq-light and itop-knownerror-light
* fix images paths comparison
* fix MD5
Were depending on platform : \ThemeHandlerTest::testGetIncludedImages test passed on Linux, not on Windows due to different DIRECTORY_SEPARATOR
- restore the initial behavior, thanks to hipska through PR#166
- refactor so as to make it clear that no SQL injection is possible (and will never be)
- add PHPUnit tests on the data synchronization => up to 20s to execute
- fix utils::ExeciTopScript to alow its usage within the automated test
a - the latest XML version is currently not correlated with the the version of iTop (though it seems to be)
b - see the converted XML... that could be saved to fix the report
- $version does not exit anymore in css-variables.css. now its value is computed during setup and equals setup timestamp instead.
- use precompiled files (declared in datamodels XML files) to check if theme compilation is required or not.
- referenced images in scss files are included in precompiled file signatures just like scss files md5sum.
- images declared in scss files with v=$version are reloaded automatically on browser side after each theme compilation (see xxx.png?v=timestamp)
- precompiled files are replaced if theme compilation occurred. this will avoid same time consuming operation at next setup.
- code cleanup: arrays / variables renamed
