Update the Magento Functional Testing Framework
This topic was updated due to the 2.3.0 MFTF release.
Magento tests and the framework are stored in different repositories.
Magento tests are stored in the same repository as the Magento code base. When you pull changes in the Magento code, you’re potentially pulling corresponding tests as well.
The MFTF is installed separately as a dependency using Composer.
When pulling the latest Magento code, update the corresponding Composer dependencies in the
magento2 root directory.
This ensures that the MFTF is up to date.
Update the MFTF from 2.3.x
To update the MFTF to the latest patch:
- Verify that the Magento WYSIWYG settings and Security settings are set appropriately.
- Check details about backward incompatible changes in the Changelog and update your new or customized tests.
Get the latest framework version using Composer:
Generate the updated tests:
Update the MFTF from 2.2
To update the MFTF from the previous minor version:
- When you update Magento, verify that the Magento WYSIWYG settings and Security settings are set appropriately.
- Starting at the
magento2/root directory remove the
rm -rf vendor/
- Get the latest framework version from the Composer dependencies:
- Remove the
rm -rf dev/tests/acceptance/vendor/
- Install dependencies at that level:
composer install -d dev/tests/acceptance/
- Run the
upgrade:testsusing the new command line tool:
vendor/bin/mftf upgrade:tests app
- If you are using Phpstorm, update the urn catalog:
vendor/bin/mftf generate:urn-catalog .idea/
- Update your own tests, including data, metadata, and so on, if they contain tags that are unsupported in the newer version. Check details about backward incompatible changes and review new MFTF release documentation in the Changelog.
- Generate newly pulled tests: