MQE-1743: Changelog and Composer Bump (#449)

- CHANGELOG update
- Version bump

Author: KevinBKozan

CHANGELOG.md

@@ -1,6 +1,40 @@
 Magento Functional Testing Framework Changelog
 ================================================
 
+2.5.0
+-----
+* Traceability
+    * Allure output has been enhanced to contain new test artifacts created and used per MFTF step:
+        * `makeScreenshot` will contain an attachment under its Allure step.
+        * `seeInCurrentUrl` and all other `Url` asserts now contain an attachment with the expects vs actual comparison.
+        * `createData` and all other `Data` actions now contain attachments with `ApiUrl`, `Headers`, `Request Body`, and `Response Body`.
+* Modularity
+    * Added a new `mftf run:manifest` command to run testManifest files generated by `generate:tests`.
+        * See DevDocs for details
+    * `mftf generate/run:test` commands now implicitly generates the `suite` the test exists in.
+        * If a test exists in multiple suites, it will generate it in all suite contexts.
+    * `mftf run:test <testName>` will now only run the exact test provided, regardless of what is generated.
+* Maintainability
+    * Added an `--allow-skipped` flag that allows MFTF to ignore the `<skip>` annotation. This was added to the following commands:
+        * `generate:test`
+        * `run:test`
+        * `run:group`
+        * `run:failed`
+* Customizability
+    * `<entity>` defined in data.xml can now reference other `<entity>` directly
+        * See DevDocs for details
+
+### Fixes
+* Fixed an issue where `grab` action variables were not substituting correctly when used as an element parameter.
+* Framework will not throw a descriptive error when referencing a `$persisted.field$` that does not exist.
+* MFTF test materials that `extends=""` itself will no longer cause infinite recursion.
+* Fixed an issue where a test could not reference a `$data.field$` whose casing was modified by the API that it used.
+* Fixed an issue with the default `functional.suite.yml` where it was incompatible with `symfony/yaml 4.0.0`.
+* Improved test generation performance via class refactors (`~10%` faster).
+
+### GitHub Issues/Pull requests:
+* [#377](https://github.com/magento/magento2-functional-testing-framework/pull/377) -- Non-API operations fixes
+
 2.4.4
 -----
 ### Fixes

bin/mftf

@@ -29,7 +29,7 @@ try {
 try {
     $application = new Symfony\Component\Console\Application();
     $application->setName('Magento Functional Testing Framework CLI');
-    $application->setVersion('2.4.4');
+    $application->setVersion('2.5.0');
     /** @var \Magento\FunctionalTestingFramework\Console\CommandListInterface $commandList */
     $commandList = new \Magento\FunctionalTestingFramework\Console\CommandList;
     foreach ($commandList->getCommands() as $command) {

composer.json

@@ -2,7 +2,7 @@
     "name": "magento/magento2-functional-testing-framework",
     "description": "Magento2 Functional Testing Framework",
     "type": "library",
-    "version": "2.4.4",
+    "version": "2.5.0",
     "license": "AGPL-3.0",
     "keywords": ["magento", "automation", "functional", "testing"],
     "config": {

composer.lock

@@ -173,6 +173,16 @@ The following is an example of a call in test:
 
 This action inputs data from the `name` of the `_defaultCategory` entity (for example, `simpleCategory598742365`) into the field with the locator defined in the selector of the `categoryNameInput` element of the `AdminCategoryBasicFieldSection`.
 
+You can also call data from the xml definition of a `data` tag directly:
+
+```xml
+<entity name="NewAdminUser" type="user">
+    <data key="username" unique="suffix">admin</data>
+    <data key="current_password">{{AnotherUser.current_password}}</data>  <!-- Data from another entity -->
+    <data key="current_password">{{_ENV.MAGENTO_ADMIN_PASSWORD}}</data>  <!-- ENV file reference -->
+</entity>
+```
+
 ## Reference
 
 ### entities {#entities-tag}