Merge pull request #2491 from magento-commerce/8-27_integration

8 27 integration

Author: dobooth

src/guides/v2.4/install-gde/prereq/mysql.md

@@ -14,7 +14,7 @@ Magento _strongly_ recommends you observe the following standard when you set up
 *  If you use MySQL database replication, be aware that Magento does _not_ support MySQL statement-based replication. Make sure you use _only_ [row-based replication](https://dev.mysql.com/doc/refman/8.0/en/replication-formats.htmll){:target="_blank"}.
 
 {:.bs-callout-warning}
-Magento 2 currently utilizes `CREATE TEMPORARY TABLE` statements inside transactions, which are [incompatible](https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-restrictions.html) with database implementations utilizing GTID-based replication, such as [Google Cloud SQL second-generation instances](https://cloud.google.com/sql/docs/features#differences).
+Magento 2 currently utilizes `CREATE TEMPORARY TABLE` statements inside transactions, which are [incompatible](https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-restrictions.html) with database implementations utilizing GTID-based replication, such as [Google Cloud SQL second-generation instances](https://cloud.google.com/sql/docs/features#differences). Consider MySQL for Cloud SQL 8.0 as an alternative.
 
 {:.bs-callout-info}
 If your web server and database server are on different hosts, perform the tasks discussed in this topic on the database server host then see [Set up a remote MySQL database connection]({{page.baseurl }}/install-gde/prereq/mysql_remote.html).

src/guides/v2.4/release-notes/open-source-2-4-3.md

@@ -708,10 +708,6 @@ We have fixed hundreds of issues in the Magento 2.4.3 core code.
 
 *  The image resizing process no longer halts for images in unsupported format. Previously, when `catalog:images:resize` encountered an unsupported image format, the process stopped and Magento displayed this error: `bin/magento catalog:images:resize Unsupported image format`.
 
-<!--- ENGCOM-9148-->
-
-*  The image resizing process now processes images marked as hidden in the Admin. Also added the `--skip_hidden_images` option to skip hidden images in the `catalog:images:resize` command. [GitHub-28239](https://github.com/magento/magento2/issues/28239)
-
 <!--- ENGCOM-8925-->
 
 *  WEBP and AVIF support for logo images has been added to the Admin. [GitHub-32495](https://github.com/magento/magento2/issues/32495)

src/guides/v2.4/security/two-factor-authentication.md

@@ -81,7 +81,7 @@ MFTF uses Google Authenticator to execute tests with 2FA enabled. The following
    bin/magento config:set twofactorauth/google/otp_window 60
    ```
 
-1. Generate a Base32-encoded string for the shared secret value.  For example, encoding the string `abcd` with the online [Base32 Encode](https://emn178.github.io/online-tools/base32_encode.html) tool returns the value `MFRGGZDF`. Use the following key to add the encoded value to the MFTF `.credentials` file:
+1. Generate a Base32-encoded string for the shared secret value.  For example, encoding the string `abcde` with the online [Base32 Encode](https://emn178.github.io/online-tools/base32_encode.html) tool returns the value `MFRGGZDF`. Use the following key to add the encoded value to the MFTF `.credentials` file:
 
    ```bash
    magento/tfa/OTP_SHARED_SECRET=MFRGGZDF

src/guides/v2.4/test/integration/annotations/magento-data-fixture.md

@@ -0,0 +1,125 @@
+---
+group: testing
+title: Data fixture annotation
+---
+
+A data fixture is a PHP script that sets data you want to reuse in your test.
+The script can be defined in a separate file or as a local test case method.
+
+Use data fixtures to prepare a database for tests.
+The Integration Testing Framework (ITF) reverts the database to its initial state automatically.
+To set up a date fixture, use the `@magentoDataFixture` annotation.
+
+## Format
+
+`@magentoDataFixture` takes an argument that points to the data fixture as a filename or local method.
+
+```php?start_inline=1
+/**
+ * @magentoDataFixture <script_filename>|<method_name>
+ */
+```
+
+-  `<script_filename>` is the filename of the PHP script.
+-  `<method_name>` is the name of the method declared in the current class.
+
+## Principles
+
+1. Do not use a direct database connection in fixtures to avoid dependencies on the database structure and vendor.
+1. Use an application API to implement your data fixtures.
+1. A method that implements a data fixture must be declared as `public` and `static`.
+1. Fixtures declared at a test level have a higher priority than fixtures declared at a test case level.
+1. Test case fixtures are applied to each test in the test case, unless a test has its own fixtures declared.
+1. Annotation declaration at a test case level does not affect tests that have their own annotation declarations.
+
+## Usage
+
+As mentioned above, there are two ways to declare fixtures:
+
+-  as a PHP script file that is used by other tests and test cases.
+-  as a local method that is used by other tests in the test cases.
+
+### Fixture as a separate file
+
+Define the fixture in a separate file when you want to reuse it in different test cases.
+To declare the fixture, use one of the following conventions:
+
+-  Fixture declaration as a path relative to the test suite directory
+   -  Relative to `dev/tests/integration/<test suite directory>`
+   -  With forward slashes `/`
+   -  No leading slash
+
+  Example:
+
+  ```php
+  /**
+   * @magentoDataFixture Magento/Cms/_files/pages.php
+   */
+  ```
+
+-  Fixture declaration as a path relative to a module
+   -  Relative to the directory of a module available in the project
+   -  With forward slashes `/`
+   -  No leading slash in the path part of the declaration
+
+  Example:
+
+  ```php
+  /**
+   * @magentoDataFixture VendorName_ModuleName::Test/Integration/_files/fixture_name.php
+   */
+  ```
+
+The ITF includes the declared PHP script to your test and executes it during the test run.
+
+The following example demonstrates a simple implementation of a Cms module page test from the Magento codebase.
+
+Data fixture to test a Cms module page: [`dev/tests/integration/testsuite/Magento/Cms/_files/pages.php`][].
+
+Test case that uses the above data fixture: [`dev/tests/integration/testsuite/Magento/Cms/Block/PageTest.php`][].
+
+### Fixture as a method
+
+[`dev/tests/integration/testsuite/Magento/Cms/Controller/PageTest.php`][] demonstrates an example of the `testCreatePageWithSameModuleName()` test method that uses data from the `cmsPageWithSystemRouteFixture()` data fixture.
+
+### Test case and test method scopes
+
+The `@magentoDataFixture` can be specified for a particular test or for an entire test case.
+The basic rules for fixture annotation at different levels are:
+
+-  `@magentoDataFixture` at a test case level, makes the framework to apply the declared fixtures to each test in the test case.
+  When the final test is complete, all class-level fixtures are reverted.
+-  `@magentoDataFixture` for a particular test, signals the framework to revert the fixtures declared on a test case level and applies the fixtures declared at a test method level instead.
+  When the test is complete, the ITF reverts the applied fixtures.
+
+ {:.bs-callout-info}
+The integration testing framework interacts with a database to revert the applied fixtures.
+
+### Fixture rollback
+
+A fixture that contains database transactions only, are reverted automatically.
+Otherwise, when a fixture creates files or performs any actions other than database transaction, provide the corresponding rollback logic.
+Rollbacks are run after reverting all the fixtures related to database transactions.
+
+A fixture rollback must be of the same format as the corresponding fixture, a script or a method:
+
+-  A rollback script must be named according to the corresponding fixture suffixed with `_rollback` and stored in the same directory.
+-  Rollback methods must be of the same class as the corresponding fixture and suffixed with `Rollback`.
+
+Examples:
+
+Fixture/Rollback | Fixture name                                         | Rollback name
+-----------------|------------------------------------------------------|-------------------------------------------------------------
+Script           | `Magento/Catalog/_files/categories.php`              | `Magento/Catalog/_files/categories_rollback.php`
+Method           | `\Magento\Catalog\Model\ProductTest::prepareProduct` | `\Magento\Catalog\Model\ProductTest::prepareProductRollback`
+
+### Restrictions
+
+Do not rely on and do not modify an application state from within a fixture, because [application isolation annotation][magentoAppIsolation] can reset the application state at any time.
+
+<!-- Link definitions -->
+
+[magentoAppIsolation]: magento-app-isolation.html
+[`dev/tests/integration/testsuite/Magento/Cms/_files/pages.php`]: {{ site.mage2bloburl }}/{{ page.guide_version }}/dev/tests/integration/testsuite/Magento/Cms/_files/pages.php
+[`dev/tests/integration/testsuite/Magento/Cms/Block/PageTest.php`]: {{ site.mage2bloburl }}/{{ page.guide_version }}/dev/tests/integration/testsuite/Magento/Cms/Block/PageTest.php
+[`dev/tests/integration/testsuite/Magento/Cms/Controller/PageTest.php`]: {{ site.mage2bloburl }}/{{ page.guide_version }}/dev/tests/integration/testsuite/Magento/Cms/Controller/PageTest.php

src/guides/v2.4/test/integration/annotations/magento-data-fixture.md

@@ -99,6 +99,33 @@ Leave all the settings that do not start with `db-` and `amqp-` at their default
 You can include additional setup options—available to the `setup:install` command—in the test configuration file. A
 complete list of options is available [here]({{ page.baseurl }}/install-gde/install/cli/install-cli.html).
 
+If your project requires custom entries in the `core_config_data` table, such as the introduction of new 3rd party services
+that affect your application on a basic level or configuration for logic that would prevent access if not configured
+properly, Magento provides a file template for this purpose.
+
+Copy `dev/tests/integration/etc/config-global.php.dist` to `dev/tests/integration/etc/config-global.php` (without the
+`.dist` suffix) and add your path-value pairs there. Do not remove existing entries from the file as they are required
+for the Integration Test Framework to run tests properly.
+
+Example:
+
+```php
+return [
+    'customer/password/limit_password_reset_requests_method' => 0,
+    'admin/security/admin_account_sharing' => 1,
+    'admin/security/limit_password_reset_requests_method' => 0,
+    'some/custom/path' => 'some-custom-value'
+];
+```
+
+Note that the file above is only for configuration files required by all integration tests. If you need to introduce
+new configuration values for particular tests to perform their function, use the
+[@magentoConfigFixture]({{ page.baseurl }}/test/integration/annotations/magento-config-fixture.html) annotation instead.
+
+{:.bs-callout-info}
+You can change the locations and names of both files used by the Integration Test Framework that were described
+above using the PHPUnit configuration file.
+
 ## Adjust the PHPUnit configuration file
 
 See the `dev/tests/integration/phpunit.xml.dist` file for the default integration test configuration.