You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/data.md
+17-6
Original file line number
Diff line number
Diff line change
@@ -74,7 +74,7 @@ This emphasizes the practice for the `stepKey` of `createData` to be descriptive
74
74
75
75
## Use data returned by test actions
76
76
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>`.
78
78
79
79
Further in the test, the data grabbed by the `someSelector` selector can be referenced using the `stepKey` value. In this case, it is `grabStepKey`.
80
80
@@ -89,7 +89,7 @@ The following example shows the usage of `grabValueFrom` in testing, where the r
89
89
90
90
The data to operate against can be included as literals in a test. Hard-coded data input can be useful in assertions.
91
91
92
-
See also [Actions](./test/actions.md).
92
+
See also [Actions][].
93
93
94
94
```xml
95
95
userInput="We'll email you an order confirmation with details and tracking info."
@@ -145,7 +145,7 @@ Example (`.../Catalog/Data/CategoryData.xml` file):
145
145
</entities>
146
146
```
147
147
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][].
149
149
150
150
All entities that have the same name will be merged during test generation. Both entities are of the `category` type.
`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">`.
189
189
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.
0 commit comments