Fixtures

A Fixture is a reusable setup/teardown block that activates when a scenario matches the fixture tag expression. Fixtures are a clean alternative to hooks when setup logic applies only to a specific group of scenarios.

Demo projects:

• https://github.com/qavajs/demo/tree/main/fixture

Basic Usage

Define a fixture in your support code:

TypeScript

import { Fixture } from '@qavajs/core';

Fixture({ name: 'pdp', tags: '@pdp' }, async function() {
    await this.playwright.page.goto('/products/qavajs-t-shirt');
});

JavaScript

const { Fixture } = require('@qavajs/core');

Fixture({ name: 'pdp', tags: '@pdp' }, async function() {
    await this.playwright.page.goto('/products/qavajs-t-shirt');
});

Fixture accepts an options object:

Property	Type	Description
name	string	fixture name (required), used in report as setup <name> / teardown <name> hook names
tags	string	tag expression that defines scenarios where the fixture is applied. If omitted, fixture is applied to all scenarios

Activate the fixture by tagging a scenario with a tag matching the fixture tag expression:

@pdp
Scenario: User adds product to cart
  When I click 'Add To Cart Button'
  Then I expect 'Cart Count' to equal '1'

Setup and Teardown

A fixture can return a teardown function that runs after the scenario completes:

TypeScript

import { Fixture } from '@qavajs/core';

Fixture({ name: 'cart', tags: '@cart' }, async function() {
    // setup: navigate to PDP and add an item
    await this.playwright.page.goto('/products/qavajs-t-shirt');
    await this.playwright.page.click('.add-to-cart');

    // teardown: remove the item after the scenario
    return async function() {
        await this.playwright.page.request.delete('/api/cart');
    }
});

JavaScript

const { Fixture } = require('@qavajs/core');

Fixture({ name: 'cart', tags: '@cart' }, async function() {
    await this.playwright.page.goto('/products/qavajs-t-shirt');
    await this.playwright.page.click('.add-to-cart');

    return async function() {
        await this.playwright.page.request.delete('/api/cart');
    }
});

Accessing Memory

Fixtures run in the world context and have full access to memory values and world properties:

TypeScript

import { Fixture } from '@qavajs/core';

Fixture({ name: 'authenticated', tags: '@authenticated' }, async function() {
    const username = await this.getValue('$username');
    const password = await this.getValue('$password');

    await this.playwright.page.goto('/login');
    await this.playwright.page.fill('#username', username);
    await this.playwright.page.fill('#password', password);
    await this.playwright.page.click('#submit');
    await this.playwright.page.waitForURL('/dashboard');

    return async function() {
        await this.playwright.page.goto('/logout');
    }
});

JavaScript

const { Fixture } = require('@qavajs/core');

Fixture({ name: 'authenticated', tags: '@authenticated' }, async function() {
    const username = await this.getValue('$username');
    const password = await this.getValue('$password');

    await this.playwright.page.goto('/login');
    await this.playwright.page.fill('#username', username);
    await this.playwright.page.fill('#password', password);
    await this.playwright.page.click('#submit');

    return async function() {
        await this.playwright.page.goto('/logout');
    }
});

Combining Multiple Fixtures

Apply multiple fixtures to a single scenario by stacking tags:

@authenticated @cart
Scenario: Logged-in user completes checkout
  When I click 'Checkout Button'
  Then I expect 'Order Confirmation' to be visible

Both fixtures will run in the order they are defined, and both teardown functions will run after the scenario.

Fixtures vs Hooks

	Fixture	Before/After Hook
Activation	Scenarios matching fixture tag expression	All scenarios (or filtered by tag expression)
Teardown	Return a function from the fixture body	Separate After hook
Visibility	Tag is visible in the feature file	Setup is invisible from the feature
Best for	Scenario-specific prerequisites	Cross-cutting concerns (screenshots, cookies)

Use fixtures when the setup belongs to a specific scenario group. Use hooks for infrastructure concerns that apply broadly across the suite.