Skip to content

Commit 1b40c8e

Browse files
authored
MQE-925: 2.2.0 CHANGELOG
- Added changelog additions for 2.2.0.
1 parent 883c327 commit 1b40c8e

File tree

1 file changed

+50
-0
lines changed

1 file changed

+50
-0
lines changed

CHANGELOG.md

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,56 @@
11
Magento Functional Testing Framework Changelog
22
================================================
33

4+
2.2.0
5+
-----
6+
### Enhancements
7+
* Traceability
8+
* Javascript errors are now logged and reported in test output.
9+
* Test failures are no longer overwritten by failures in an `<after>` hook.
10+
* Tests will no longer execute an `<after>` hook twice if a failure triggered in the `<after>` hook.
11+
* Tests marked with `<group value="skip">` will now appear in generated Allure reports.
12+
* Along with the above, the `robo group` command no longer omits the `skip` group (skipped tests are picked up but not fully executed).
13+
* Modularity
14+
* MFTF no longer relies on relative pathing to determine its path to tests or Magento (favoring composer information if available).
15+
* Tests and test materials are now read in from Magento modules as well as extensions in addition to `dev/tests/acceptance`.
16+
* See DevDocs `Getting Started` for details on expected paths and merge order.
17+
* Customizability
18+
* Creation of Suites is now supported
19+
* `<suite>` can include tests via `name`, module, or `<group>` tags.
20+
* Consolidation of preconditions can be achieved via use of `<before/after>` tags in a `<suite>`
21+
* All normal test actions are supported
22+
* Data returned from actions is not available for reference in subsequent tests (`createData` or `grab` actions).
23+
* `robo generate:tests` generates all suites and tests, and can be given a JSON configuration to generate specific test/suites.
24+
* See MFTF Devdocs "Suite" page for more details.
25+
* `<deleteData>` may now be called against a `url` instead of a stepKey reference.
26+
* `<dragAndDrop>` may now be given an additional `x/y` offset.
27+
* `<executeJS>` now returns a variable based on what the executed script returns.
28+
* Added `<element>` `type="block"`.
29+
* `<page>` elements may now be blank (contain no child sections).
30+
* Maintainability
31+
* `robo generate:tests --config parallel` now accepts a `--lines` argument, for grouping and sorting based on test length.
32+
* `robo generate:tests` now checks for:
33+
* Duplicate step keys within an `actionGroup`.
34+
* Ambiguous or invalid `stepKey` references (in merge files).
35+
* `robo generate:tests` now suppresses warnings by default. The command now accepts a `--verbose` flag to show full output including warnings.
36+
37+
### Fixes
38+
* Exception message for the `<conditionalClick>` action now correctly references the `selector` given.
39+
* Usage of multiple parameterized elements in a `selector` now correctly resolves all element references.
40+
* Usage of multiple uniqueness references on the same entity now generate correctly.
41+
* Persisted entity references are correctly interpolated with `<page>` url of `type="admin"`.
42+
* Metadata that contains 2 or more params in its `url` now correctly resolve parameters.
43+
* Arguments can now be passed to `x` and `y` attributes in `actionGroup`.
44+
* Arguments can now be passed to nested `<assert*>` action elements.
45+
* The `<seeInField>` action can now be used to assert against empty strings.
46+
* Empty `<data>` elements within an `<entity>` now generate correctly.
47+
* Mapping of the `<magentoCLI>` to the custom command has been fixed.
48+
49+
### GitHub Issues/Pull requests:
50+
* [#89](https://github.com/magento/magento2-functional-testing-framework/pull/89) -- Add ability to use array entities as arguments.
51+
* [#68](https://github.com/magento/magento2-functional-testing-framework/issues/68) -- Excessive double quotes are being generated in WaitForElementChange method arguments (fixed in [#103](https://github.com/magento/magento2-functional-testing-framework/pull/103))
52+
* [#31](https://github.com/magento/magento2-functional-testing-framework/issues/31) -- Can't run tests without a store having "default" store code (fixed in [#86](https://github.com/magento/magento2-functional-testing-framework/pull/86))
53+
454
2.1.2
555
-----
656
### Enhancements

0 commit comments

Comments
 (0)