|
1 | 1 | Magento Functional Testing Framework Changelog
|
2 | 2 | ================================================
|
3 | 3 |
|
| 4 | +2.3.0 |
| 5 | +----- |
| 6 | +### Enhancements |
| 7 | +* Traceability |
| 8 | + * MFTF now outputs generation run-time information, warnings, and errors to an `mftf.log` file. |
| 9 | + * Overall error messages for various generation errors have been improved. Usage of the `--debug` flag provides file-specific errors for all XML-related errors. |
| 10 | + * Allure Reports now require a unique `story` and `title` combination, to prevent collisions in Allure Report generation. |
| 11 | + * The `features` annotation now ignores user input and defaults to the module the test lives under (for clear Allure organization). |
| 12 | + * The `<group value="skip"/>` annotation has been replaced with a `<skip>` annotation, allowing for nested `IssueId` elements. |
| 13 | + * Tests now require the following annotations: `stories`, `title`, `description`, `severity`. |
| 14 | + * This will be enforced in a future major release. |
| 15 | +* Modularity |
| 16 | + * MFTF has been decoupled from MagentoCE: |
| 17 | + * MFTF can now generate and run tests by itself via `bin/mftf` commands. |
| 18 | + * It is now a top level MagentoCE dependency, and no longer relies on supporting files in MagentoCE. |
| 19 | + * It can be used as an isolated dependency for Magento projects such as extensions. |
| 20 | + * `generate:tests` now warns the user if any declared `<page>` has an inconsistent `module` (`Backend` vs `Magento_Backend`) |
| 21 | + * The `--force` flag now completely ignores checking of the Magento Installation, allowing generation of tests without a Magento Instance to be running. |
| 22 | +* Customizability |
| 23 | + * Various test materials can now be extended via an `extends="ExistingMaterial"` attribute. This allows for creation of simple copies of any `entity`, `actionGroup`, or `test`, with small modifications. |
| 24 | + * `test` and `actionGroup` deltas can now be provided in bulk via a `before/after` attribute on the `test` or `actionGroup` element. Deltas provided this way do not need individual `before/after` attributes, and are inserted sequentially. |
| 25 | + * Secure and sensitive test data can now be stored and used via a new `.credentials` file, with declaration and usage syntax similar to `.env` file references. |
| 26 | + * A new `<generateDate>` action has been added to allow users to create and use dates according to the given `date` and `format`. |
| 27 | + * See DevDocs for more information on all above `Customizability` features. |
| 28 | +* Maintainability |
| 29 | + * New `bin/mftf` commands have been introduced with parity to existing `robo` commands. |
| 30 | + * `robo` commands are still supported, but will be deprecated in a future major release. |
| 31 | + * The `mftf upgrade:tests` command has been introduced, which runs all test upgrade scripts against the provided path. |
| 32 | + * A new upgrade script was created to replace all test material schema paths to instead use a URN path. |
| 33 | + * The `mftf generate:urn-catalog` command has been introduced to create a URN catalog in PHPStorm to support the above upgrade. |
| 34 | + * A warning is now shown on generation if a page's url is referenced without specifying the url (`{{page}}` vs `{{page.url}}`). |
| 35 | + * An error is now thrown if any test materials contain any overriding element (eg different `<element>`s in a `<section>` with the same `name`) |
| 36 | + * This previously would cause the last read element to override the previous, causing a silent but potentially incorrect test addition. |
| 37 | + * Test distribution algorithm for `--config parallel` has been enhanced to take average step length into account. |
| 38 | + |
| 39 | +### Fixes |
| 40 | +* `_after` hook of tests now executes if a non test-related failure causes the test to error. |
| 41 | +* Fixed periods in Allure Report showing up as `•`. |
| 42 | +* Fixed Windows incompatibility of relative paths in various files. |
| 43 | +* Suites will no longer generate if they do not contain any tests. |
| 44 | +* Fixed an issue in generation where users could not use javascript variables in `executeJS` actions. |
| 45 | +* Fixed an issue in generation where entity replacement in action-groups replaced all entities with the first reference found. |
| 46 | +* Fixed an issue in generation where `createData` actions inside `actionGroups` could not properly reference the given `createDataKey`. |
| 47 | +* Fixed an issue where `suites` could not generate if they included an `actionGroup` with two arguments. |
| 48 | +* Fixed an issue in generation where calling the same entity twice (with different parameters) would replace both calls with the first resolved value. |
| 49 | +* The `magentoCLI` action now correctly executes the given command if the `MAGENTO_BASE_URL` contains `index.php` after the domain (ex `https://magento.instance/index.php`) |
| 50 | +* The `stepKey` attribute can no longer be an empty. |
| 51 | +* Variable substitution has been enabled for `regex` and `command` attributes in test actions. |
| 52 | + |
| 53 | +### GitHub Issues/Pull requests: |
| 54 | +* [#161](https://github.com/magento/magento2-functional-testing-framework/pull/161) -- MAGETWO-46837: Implementing extension to wait for readiness metrics. |
| 55 | +* [#72](https://github.com/magento/magento2-functional-testing-framework/issues/72) -- declare(strict_types=1) causes static code check failure (fixed in [#154](https://github.com/magento/magento2-functional-testing-framework/pull/154)) |
| 56 | + |
4 | 57 | 2.2.0
|
5 | 58 | -----
|
6 | 59 | ### Enhancements
|
|
0 commit comments