commerce-docs · imgbot · Aug 30, 2022 · Aug 30, 2022 · Dec 7, 2022 · Dec 8, 2022
diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
@@ -3,7 +3,10 @@
 
 name: CI
 
-on: [pull_request]
+on:
+  pull_request:
+    paths-ignore:
+      - 'docs/**'
 
 jobs:
   unit-tests:

diff --git a/docs/backward-incompatible-changes.md b/docs/backward-incompatible-changes.md
@@ -1,3 +1,9 @@
+---
+title: MFTF 3.0.0 backward incompatible changes
+redirect_to: https://developer.adobe.com/commerce/testing/functional-testing-framework/backward-incompatible-changes/
+status: migrated
+---
+
 # MFTF 3.0.0 backward incompatible changes
 
 This page highlights backward incompatible changes between releases that have a major impact and require detailed explanation and special instructions to ensure third-party tests continue working with Magento core tests.

diff --git a/docs/best-practices.md b/docs/best-practices.md
@@ -1,3 +1,9 @@
+---
+title: Best practices
+redirect_to: https://developer.adobe.com/commerce/testing/functional-testing-framework/test-writing/best-practices/
+status: migrated
+---
+
 # Best practices
 
 Check out our best practices below to ensure you are getting the absolute most out of the Magento Functional Testing Framework.
@@ -85,7 +91,7 @@ The following pattern is used when merging with `extends`:
  Use a corresponding [`<deleteData>`] test step in your [`<after>`] block when using a [`<createData>`] action in a [`<before>`] block.
 2. Make specific data entries under test to be unique.
  Enable data uniqueness where data values are required to be unique in a database by test design.
- Use `unique=”suffix”` or `unique=”prefix”` to append or prepend a unique value to the [entity] attribute.
+ Use `unique="suffix"` or `unique="prefix"` to append or prepend a unique value to the [entity] attribute.
  This ensures that tests using the entity can be repeated.
 3. Do not modify existing data entity fields or merge additional data fields without complete understanding and verifying the usage of existing data in tests.
  Create a new data entity for your test if you are not sure.

diff --git a/docs/commands/codeception.md b/docs/commands/codeception.md
@@ -1,3 +1,9 @@
+---
+title: CLI commands - vendor/bin/codecept
+redirect_to: https://developer.adobe.com/commerce/testing/functional-testing-framework/commands/codeception/
+status: migrated
+---
+
 # CLI commands: vendor/bin/codecept
 
 <div class="bs-callout bs-callout-warning" markdown="1">

diff --git a/docs/commands/mftf.md b/docs/commands/mftf.md
@@ -1,3 +1,9 @@
+---
+title: CLI commands - vendor/bin/mftf
+redirect_to: https://developer.adobe.com/commerce/testing/functional-testing-framework/commands/mftf/
+status: migrated
+---
+
 # CLI commands: vendor/bin/mftf
 
 The Magento Functional Testing Framework (MFTF) introduces the command line interface (CLI) tool `vendor/bin/mftf` to facilitate your interaction with the framework.

diff --git a/docs/configuration.md b/docs/configuration.md
@@ -1,3 +1,9 @@
+---
+title: Configuration
+redirect_to: https://developer.adobe.com/commerce/testing/functional-testing-framework/configuration/
+status: migrated
+---
+
 # Configuration
 
 The `*.env` file provides additional configuration for the Magento Functional Testing Framework (MFTF).

diff --git a/docs/configure-2fa.md b/docs/configure-2fa.md
@@ -1,3 +1,9 @@
+---
+title: Configuring MFTF for two-factor authentication (2FA)
+redirect_to: https://developer.adobe.com/commerce/testing/functional-testing-framework/two-factor-authentication/
+status: migrated
+---
+
 # Configuring MFTF for Two-Factor Authentication (2FA)
 
 Using two-factor authentication (2FA) with MFTF is possible with some configurations settings in Magento.

diff --git a/docs/credentials.md b/docs/credentials.md
@@ -1,3 +1,9 @@
+---
+title: Credentials
+redirect_to: https://developer.adobe.com/commerce/testing/functional-testing-framework/credentials/
+status: migrated
+---
+
 # Credentials
 
 When you test functionality that involves external services such as UPS, FedEx, PayPal, or SignifyD,

diff --git a/docs/custom-helpers.md b/docs/custom-helpers.md
@@ -1,3 +1,9 @@
+---
+title: Custom helpers
+redirect_to: https://developer.adobe.com/commerce/testing/functional-testing-framework/custom-helpers/
+status: migrated
+---
+
 # Custom Helpers
 
 <div class="bs-callout-warning">
@@ -37,7 +43,7 @@ This functionality is used to select text on the page and cannot be accomplished
 ```php
 <?php
 /**
- * Copyright © Magento, Inc. All rights reserved.
+ * Copyright &copy; Magento, Inc. All rights reserved.
  * See COPYING.txt for license details.
  */
 

diff --git a/docs/data.md b/docs/data.md
@@ -1,3 +1,9 @@
+---
+title: Input testing data
+redirect_to: https://developer.adobe.com/commerce/testing/functional-testing-framework/data/
+status: migrated
+---
+
 # Input testing data
 
 MFTF enables you to specify and use `<data>` entities defined in XML. Default `<data>` entities are provided for use and as templates for entity creation and manipulation.

diff --git a/docs/debugging.md b/docs/debugging.md
@@ -1,3 +1,9 @@
+---
+title: Debugging
+redirect_to: https://developer.adobe.com/commerce/testing/functional-testing-framework/debugging/
+status: migrated
+---
+
 # Debugging
 
 Debugging within the Magento Functional Testing Framework is helpful in identifying test bugs by allowing you to pause execution so that you may:

diff --git a/docs/extending.md b/docs/extending.md
@@ -1,3 +1,9 @@
+---
+title: Extending
+redirect_to: https://developer.adobe.com/commerce/testing/functional-testing-framework/extending/
+status: migrated
+---
+
 # Extending
 
 There are cases when you need to create many tests that are very similar to each other.

diff --git a/docs/getting-started.md b/docs/getting-started.md
@@ -1,3 +1,9 @@
+---
+title: Getting started
+redirect_to: https://developer.adobe.com/commerce/testing/functional-testing-framework/getting-started/
+status: migrated
+---
+
 # Getting started
 
 <div class="bs-callout bs-callout-info" markdown="1">

diff --git a/docs/guides/action-groups.md b/docs/guides/action-groups.md
@@ -1,3 +1,9 @@
+---
+title: Action group best practices
+redirect_to: https://developer.adobe.com/commerce/testing/functional-testing-framework/test/action-group-best-practices/
+status: migrated
+---
+
 # Action Group Best Practices
 
 We strive to write tests using only action groups. Fortunately, we have built up a large set of action groups to get started. We can make use of them and extend them for our own specific needs. In some cases, we may never even need to write action groups of our own. We may be able to simply chain together calls to existing action groups to implement our new test case.

diff --git a/docs/guides/cicd.md b/docs/guides/cicd.md
@@ -1,3 +1,9 @@
+---
+title: How to use MFTF in CICD
+redirect_to: https://developer.adobe.com/commerce/testing/functional-testing-framework/cicd/
+status: migrated
+---
+
 # How to use MFTF in CICD
 
 To integrate MFTF tests into your CICD pipeline, it is best to start with the conceptual flow of the pipeline code.

diff --git a/docs/guides/git-vs-composer-install.md b/docs/guides/git-vs-composer-install.md
@@ -1,3 +1,9 @@
+---
+title: Git vs Composer installation of Magento with MFTF
+redirect_to: https://developer.adobe.com/commerce/testing/functional-testing-framework/git-vs-composer-install/
+status: migrated
+---
+
 # Git vs Composer installation of Magento with MFTF
 
 Depending on how you plan to use Magnto code, there are different options for installing Magento.

diff --git a/docs/guides/selectors.md b/docs/guides/selectors.md
@@ -1,3 +1,9 @@
+---
+title: How to write good selectors
+redirect_to: https://developer.adobe.com/commerce/testing/functional-testing-framework/test-writing/selectors/
+status: migrated
+---
+
 # How To write good selectors
 
 Selectors are the atomic unit of test writing. They fit into the hierarchy like this: MFTF tests make use of action groups > which are made up of actions > which interact with page objects > which contain elements > which are specified by selectors. Because they are fundamental building blocks, we must take care when writing them.
@@ -213,7 +219,7 @@ Similarly, the relative XPath selector is a double forward slash `//`. It is use
 Example:
 
 ```xpath
-//div[@class=’form-group’]//input[@id='user-message']
+//div[@class='form-group']//input[@id='user-message']
 ```
 
 In the `GOOD` example above, all `<div class='form-group'/>` elements in the DOM are matched first. Then all `<input id='user-message'/>` with `<div class='form-group'/>` as one of its parents are matched. The parent does not have to immediately precede it since it uses another double forward slash `//`.
@@ -247,7 +253,7 @@ Given this HTML:
 ```html
 <tr>
     <td>
-        <a href=“#”>Edit</a>
+        <a href="#">Edit</a>
     </td>
     <td>
         <div>Unique Value</div>

diff --git a/docs/guides/test-isolation.md b/docs/guides/test-isolation.md
@@ -1,3 +1,9 @@
+---
+title: Test isolation
+redirect_to: https://developer.adobe.com/commerce/testing/functional-testing-framework/test-writing/test-isolation/
+status: migrated
+---
+
 # Test Isolation
 
 Because MFTF is a framework for testing a highly customizable and ever changing application, MFTF tests need to be properly isolated.

diff --git a/docs/guides/test-modularity.md b/docs/guides/test-modularity.md
@@ -1,3 +1,9 @@
+---
+title: Test modularity
+redirect_to: https://developer.adobe.com/commerce/testing/functional-testing-framework/test-writing/test-modularity/
+status: migrated
+---
+
 # Test Modularity
 
 One of MFTF's most distinguishing functionalities is the framework's modularity.

diff --git a/docs/guides/using-suites.md b/docs/guides/using-suites.md
@@ -1,3 +1,9 @@
+---
+title: Using suites
+redirect_to: https://developer.adobe.com/commerce/testing/functional-testing-framework/test-writing/using-suites/
+status: migrated
+---
+
 # Using suites
 
 With an increasing number of MFTF tests, it is important to have a mechanism to organize and consolidate them for ease-of-use.