Fixtures

 In Playwright, a fixture refers to a predefined setup or configuration that provides the context for your tests. Fixtures are used to define the environment in which tests run, ensuring that necessary prerequisites are in place before the execution of each test or suite of tests. Fixtures can include actions like launching a browser, setting up test data, initializing objects, or any other setup needed to ensure consistent and reliable test execution.

Key Concepts of Fixtures in Playwright

1. Setup and Teardown: Fixtures handle the setup and teardown processes, making sure that the environment is correctly prepared before a test runs and cleaned up afterward.
2. Isolation: Fixtures help isolate tests from each other, ensuring that tests do not interfere with one another by sharing the same state or data.
3. Reusable Configurations: Fixtures allow for the reuse of common setups across multiple tests, reducing redundancy and making the test code cleaner and more maintainable.

Normally, if all tests pass and no errors are thrown, the order of execution is as following.

• worker setup and beforeAll section:
  • browser setup because it is required by autoWorkerFixture.
  • autoWorkerFixture setup because automatic worker fixtures are always set up before anything else.
  • beforeAll runs.
• first test section:
  • autoTestFixture setup because automatic test fixtures are always set up before test and beforeEach hooks.
  • page setup because it is required in beforeEach hook.
  • beforeEach runs.
  • first test runs.
  • afterEach runs.
  • page teardown because it is a test-scoped fixture and should be torn down after the test finishes.
  • autoTestFixture teardown because it is a test-scoped fixture and should be torn down after the test finishes.
• second test section:
  • autoTestFixture setup because automatic test fixtures are always set up before test and beforeEach hooks.
  • page setup because it is required in beforeEach hook.
  • beforeEach runs.
  • workerFixture setup because it is required by testFixture that is required by the second test.
  • testFixture setup because it is required by the second test.
  • second test runs.
  • afterEach runs.
  • testFixture teardown because it is a test-scoped fixture and should be torn down after the test finishes.
  • page teardown because it is a test-scoped fixture and should be torn down after the test finishes.
  • autoTestFixture teardown because it is a test-scoped fixture and should be torn down after the test finishes.
• afterAll and worker teardown section:
  • afterAll runs.
  • workerFixture teardown because it is a workers-scoped fixture and should be torn down once at the end.
  • autoWorkerFixture teardown because it is a workers-scoped fixture and should be torn down once at the end.
  • browser teardown because it is a workers-scoped fixture and should be torn down once at the end.