|
1 | 1 | Magento Functional Testing Framework Changelog |
2 | 2 | ================================================ |
3 | 3 |
|
| 4 | +2.5.1 |
| 5 | +----- |
| 6 | + |
| 7 | +### Fixes |
| 8 | +* Fixed missing `use` statement in the generate:suite command |
| 9 | + |
| 10 | +### GitHub Issues |
| 11 | +* [#471](https://github.com/magento/magento2-functional-testing-framework/issues/471) -- PHP Fatal error: MftfApplicationConfig not found in GenerateSuiteCommand |
| 12 | + |
| 13 | +2.5.0 |
| 14 | +----- |
| 15 | +* Traceability |
| 16 | + * Allure output has been enhanced to contain new test artifacts created and used per MFTF step: |
| 17 | + * `makeScreenshot` will contain an attachment under its Allure step. |
| 18 | + * `seeInCurrentUrl` and all other `Url` asserts now contain an attachment with the expects vs actual comparison. |
| 19 | + * `createData` and all other `Data` actions now contain attachments with `Request Body` and `Response Body`. |
| 20 | +* Modularity |
| 21 | + * Added a new `mftf run:manifest` command to run testManifest files generated by `generate:tests`. |
| 22 | + * See DevDocs for details |
| 23 | + * `mftf generate/run:test` commands now implicitly generates the `suite` the test exists in. |
| 24 | + * If a test exists in multiple suites, it will generate it in all suite contexts. |
| 25 | + * `mftf run:test <testName>` will now only run the exact test provided, regardless of what is generated. |
| 26 | +* Maintainability |
| 27 | + * Added an `--allow-skipped` flag that allows MFTF to ignore the `<skip>` annotation. This was added to the following commands: |
| 28 | + * `generate:test` |
| 29 | + * `run:test` |
| 30 | + * `run:group` |
| 31 | + * `run:failed` |
| 32 | +* Customizability |
| 33 | + * `<entity>` defined in data.xml can now reference other `<entity>` directly. |
| 34 | + * See DevDocs for details |
| 35 | + * Added vault as an alternative credential storage. |
| 36 | + * See DevDocs for details |
| 37 | + |
| 38 | +### Fixes |
| 39 | +* Fixed an issue where `grab` action variables were not substituting correctly when used as an element parameter. |
| 40 | +* Framework will not throw a descriptive error when referencing a `$persisted.field$` that does not exist. |
| 41 | +* MFTF test materials that `extends=""` itself will no longer cause infinite recursion. |
| 42 | +* Fixed an issue where a test could not reference a `$data.field$` whose casing was modified by the API that it used. |
| 43 | +* Fixed an issue with the default `functional.suite.yml` where it was incompatible with `symfony/yaml 4.0.0`. |
| 44 | +* Improved test generation performance via class refactors (`~10%` faster). |
| 45 | + |
| 46 | +### GitHub Issues/Pull requests: |
| 47 | +* [#377](https://github.com/magento/magento2-functional-testing-framework/pull/377) -- Non-API operations fixes |
| 48 | + |
| 49 | +2.4.5 |
| 50 | +----- |
| 51 | +### Fixes |
| 52 | +* Fixed an issue where `.credentials` was required when using `<createData>` actions with field overrides. |
| 53 | + |
| 54 | +2.4.4 |
| 55 | +----- |
| 56 | +### Fixes |
| 57 | +* Fixed an issue where `_CREDS` could not be resolved when used in a suite. |
| 58 | + |
| 59 | +2.4.3 |
| 60 | +----- |
| 61 | +* Customizability |
| 62 | + * Use of `_CREDS` has been extended to `<magentoCLI>` and `<createData>` actions |
| 63 | +* Traceability |
| 64 | + * A Test step is now generated and injected in the allure report when a test is reported as `BROKEN`. |
| 65 | + |
| 66 | +### Fixes |
| 67 | +* `static-checks` command now properly returns `1` if any static check failed. |
| 68 | +* MFTF Console Printer class correctly utilizes `--steps` and other flags passed directly to `codecept commands`. |
| 69 | +* `*source` actions correctly print when using `userInput` or `html` attributes. |
| 70 | +* XML Comments should no longer throw an error in parsing when used outside `test/actionGroup` |
| 71 | + |
| 72 | +### GitHub Issues/Pull requests: |
| 73 | +* [#703](https://github.com/magento/magento2-functional-testing-framework/pull/403) -- SMALL_CHANGE: Minor change suggested |
| 74 | + |
| 75 | +2.4.2 |
| 76 | +----- |
| 77 | +* Traceability |
| 78 | + * Test action `stepKey`s are now included in both console output and Allure report. |
| 79 | + * XML Comments are now automatically converted into a `<comment>` action. |
| 80 | + |
| 81 | +### Fixes |
| 82 | +* Moved `epfremme/swagger-php` dependency to `suggests` block due to a conflict with Magento extensions. |
| 83 | + |
| 84 | +2.4.1 |
| 85 | +----- |
| 86 | +* Traceability |
| 87 | + * XSD Schema validation is now enabled by default in `generate:tests`, `run:test`, `run:failed`, `run:group` |
| 88 | + * `--debug` option for the above commands has been updated to include different debug levels |
| 89 | + * See DevDocs for details |
| 90 | + |
| 91 | +### Fixes |
| 92 | +* Fixed an issue where `skipReadiness` attribute would cause false XSD Schema validation errors. |
| 93 | + |
4 | 94 | 2.4.0 |
5 | 95 | ----- |
6 | 96 | ### Enhancements |
|
0 commit comments