Skip to content

Commit bd990cc

Browse files
authored
Merge branch 'develop' into MQE-1457
2 parents 2c84791 + 9b5d79c commit bd990cc

7 files changed

+18
-7
lines changed

docs/commands/codeception.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Run all tests without the `<group value="skip"/>` [annotation][]:
2121
vendor/bin/codecept run functional --skip-group skip -c dev/tests/acceptance/codeception.yml
2222
```
2323

24-
Run all tests with the `<group value="example"/>` [annotation][] but with no `<group value="skpip"/>`:
24+
Run all tests with the `<group value="example"/>` [annotation][] but with no `<group value="skip"/>`:
2525

2626
```bash
2727
vendor/bin/codecept run functional --group example --skip-group skip -c dev/tests/acceptance/codeception.yml

docs/data.md

+17-6
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ This emphasizes the practice for the `stepKey` of `createData` to be descriptive
7474

7575
## Use data returned by test actions
7676

77-
A test can also reference data that was returned as a result of [test actions](./test/actions.md#actions-returning-a-variable), like the action `<grabValueFrom selector="someSelector" stepKey="grabStepKey>`.
77+
A test can also reference data that was returned as a result of [test actions][], like the action `<grabValueFrom selector="someSelector" stepKey="grabStepKey>`.
7878

7979
Further in the test, the data grabbed by the `someSelector` selector can be referenced using the `stepKey` value. In this case, it is `grabStepKey`.
8080

@@ -89,7 +89,7 @@ The following example shows the usage of `grabValueFrom` in testing, where the r
8989

9090
The data to operate against can be included as literals in a test. Hard-coded data input can be useful in assertions.
9191

92-
See also [Actions](./test/actions.md).
92+
See also [Actions][].
9393

9494
```xml
9595
userInput="We'll email you an order confirmation with details and tracking info."
@@ -145,7 +145,7 @@ Example (`.../Catalog/Data/CategoryData.xml` file):
145145
</entities>
146146
```
147147

148-
This example declares two `<data>` entities: `_defaultCategory` and `SimpleSubCategory`. They set the data required for [category creation](http://docs.magento.com/m2/ce/user_guide/catalog/category-create.html).
148+
This example declares two `<data>` entities: `_defaultCategory` and `SimpleSubCategory`. They set the data required for [category creation][].
149149

150150
All entities that have the same name will be merged during test generation. Both entities are of the `category` type.
151151

@@ -187,7 +187,7 @@ Attributes|Type|Use|Description
187187
`name`|string|optional|Name of the `<entity>`.
188188
`type`|string|optional|Node containing the exact name of `<entity>` type. Used later to find specific Persistence Layer Model class. `type` in `<data>` can be whatever the user wants; There are no constraints. It is important when persisting data, depending on the `type` given, as it will try to match a metadata definition with the operation being done. Example: A `myCustomer` entity with `type="customer"`, calling `<createData entity="myCustomer"/>`, will try to find a metadata entry with the following attributes: `<operation dataType="customer" type="create">`.
189189

190-
`<entity>` may contain one or more [`<data>`](#data-tag), [`<var>`](#var-tag), [`<required-entities>`](#requiredentity-tag), or [`<array>`](#array-tag) elements in any sequence.
190+
`<entity>` may contain one or more [`<data>`][], [`<var>`][], [`<required-entities>`][], or [`<array>`][] elements in any sequence.
191191

192192
### data {#data-tag}
193193

@@ -248,8 +248,19 @@ Attributes|Type|Use|Description
248248
---|---|---|---
249249
`key`|string|required|Key attribute of this entity in which to assign a value.
250250

251-
`<array>` may contain [`<item>`](#item-tag) elements.
251+
`<array>` may contain [`<item>`][] elements.
252252

253253
### item {#item-tag}
254254

255-
`<item>` is an individual piece of data to be passed in as part of the parent `<array>` type.
255+
`<item>` is an individual piece of data to be passed in as part of the parent `<array>` type.
256+
257+
<!-- Link Definitions -->
258+
[`<array>`]: #array-tag
259+
[`<data>`]: #data-tag
260+
[`<item>`]: #item-tag
261+
[`<required-entities>`]: #requiredentity-tag
262+
[`<var>`]: #var-tag
263+
[Actions]: ./test/actions.md
264+
[category creation]: http://docs.magento.com/m2/ce/user_guide/catalog/category-create.html
265+
[Credentials]: ./credentials.md
266+
[test actions]: ./test/actions.md#actions-returning-a-variable
-1.94 KB
Loading

docs/img/issue.png

-2.28 KB
Loading

docs/img/pull-request.png

-1.34 KB
Loading

docs/img/switching-the-base.png

-1.43 KB
Loading

docs/img/trouble-chrome232.png

-19.7 KB
Loading

0 commit comments

Comments
 (0)