Application isolation annotation

An application state can be changed during test execution. Such changes can cause a false test failure.

The integration testing framework keeps the tests isolated and provides optimal performance by default. Isolation is managed using the @magentoAppIsolation annotation.

Format

Application isolation annotation:

Copy
/**
 * @magentoAppIsolation enabled|disabled
 */
Copied to your clipboard
/**
 * @magentoAppIsolation enabled|disabled
 */

Test case annotation

The application and related objects are reinitialized after each test case execution. This behavior helps to isolate application objects in different test cases. The test case isolation is mandatory and cannot be disabled.

Test annotation

By default, the application isolation (that is automatic reinitialization) in tests is disabled. To enable the application isolation for a test, use the @magentoAppIsolation annotation.

Example:

Copy
/**
 * @magentoAppIsolation enabled
 */
public function testGetAddressById()
{
    $addressId = 2;
    $address = $this->repository->getById($addressId);
    $this->assertEquals($this->_expectedAddresses[1], $address);
}
Copied to your clipboard
/**
 * @magentoAppIsolation enabled
 */
public function testGetAddressById()
{
    $addressId = 2;
    $address = $this->repository->getById($addressId);
    $this->assertEquals($this->_expectedAddresses[1], $address);
}

Defaults

Default values for the @magentoAppIsolation annotation:

@magentoAppIsolation cannot be disabled at the test case level.

You can use non-isolated tests unless they do not modify or utilize the same application areas such as:

• same attributes of an application object.
• same paths in a current configuration or current scope (for example "store").

Last updated 9/11/2023

Was this helpful?

Yes

No