Skip to content

Commit 7b57266

Browse files
soumyaudobooth
andauthored
MQE-2218: Part 5 Docs Annual Review (#764)
* MQE-2218: Part 5 Docs Annual Review * Grammar tweak Co-authored-by: Donald Booth <[email protected]>
1 parent ddf5564 commit 7b57266

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

docs/best-practices.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -37,11 +37,9 @@ We recommend to keep Action Groups having single responsibility, for example `Ad
3737

3838
## Contribute
3939

40-
Althought the Magento Core team and Contributors join forces to cover most of the features with tests, it is impossible to have this done quickly.
40+
Although the Magento Core team and Contributors join forces to cover most of the features with tests, it is impossible to have this done quickly.
4141
If you've covered Magento Core feature with Functional Tests - you are more than welcome to contribute.
4242

43-
You can also help with MFTF Test Migration to get the experience and valuable feedback from other community members and maintainers.
44-
4543
## Action group
4644

4745
1. [Action group] names should be sufficiently descriptive to inform a test writer of what the action group does and when it should be used. Add additional explanation in annotations if needed.
@@ -108,7 +106,7 @@ Example: _StorefrontCreateCustomerTest.xml_.
108106

109107
#### Action Group file name
110108

111-
Format: {_Admin_ or _Storefront_}{Action Group Summary}ActionGroup.xml`, where Action Group Summary describes with a few words what we can expect from it.
109+
Format: {_Admin_ or _Storefront_}{Action Group Summary}ActionGroup.xml`, where Action Group Summary is a short description of what the action group does.
112110

113111
Example: _AdminCreateStoreActionGroup.xml_
114112

0 commit comments

Comments
 (0)