Application isolation attribute

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 AppIsolation attribute.

Format

Copy
#[
    AppIsolation(bool $state = true)
]
Copied to your clipboard
#[
    AppIsolation(bool $state = true)
]

Parameters

• state
  • Accepts TRUE or FALSE to enable or disable app isolation respectively.

Test class attribute

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

Test method

By default, the application isolation (that is automatic reinitialization) in tests method is disabled. To enable the application isolation for a test method, use the AppIsolation attribute.

Example:

Copy
#[
    AppIsolation(true)
]
public function testGetAddressById()
{
    $addressId = 2;
    $address = $this->repository->getById($addressId);
    $this->assertEquals($this->_expectedAddresses[1], $address);
}
Copied to your clipboard
#[
    AppIsolation(true)
]
public function testGetAddressById()
{
    $addressId = 2;
    $address = $this->repository->getById($addressId);
    $this->assertEquals($this->_expectedAddresses[1], $address);
}

Defaults

Default values for the AppIsolation attribute:

AppIsolation cannot be disabled at the test class 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