Create playwright test data

Skill jeffsenso/prestashop-skills/skills/prestashop-module-development/ps9-core-ai/Component/Playwright/skills/create-playwright-test-data

Prestashop Developer Skills

Install

npx -y skills add jeffsenso/prestashop-skills --skill create-playwright-test-data

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create Faker data classes and predefined data objects for a new entity in the ui-testing-library. These are imported by campaigns for consistent test data generation. Trigger: "create test data for {Domain}".

SKILL.md

2.3 KB, as published. Nobody here has run it

create-playwright-test-data

Read @.ai/Component/Playwright/CONTEXT.md for the stack and data patterns.

Faker data classes and predefined data objects live in the ui-testing-library, not in the core repo.

1. Faker data class

Create Faker{Domain} in the ui-testing-library:

Constructor accepts optional overrides: new FakerTax({enabled: false})
Default values use Faker for randomized but realistic data
Properties match the entity fields (name, active, rate, etc.)
Multilingual fields include values for at least EN and FR

// Usage in campaigns:
const createTaxData: FakerTax = new FakerTax();
const editTaxData: FakerTax = new FakerTax({enabled: false});

Reference: check existing Faker classes in the ui-testing-library (e.g. FakerTax, FakerProduct)

2. Predefined data objects

Create data{Domain} objects referencing demo install fixtures:

// Usage in campaigns:
import {dataTaxes} from '@prestashop-core/ui-testing';
dataTaxes.DefaultFrTax.id;
dataTaxes.DefaultFrTax.name;

These reference entities that exist in the vanilla PrestaShop installation — useful for tests that filter/sort existing data rather than creating new entities.

3. Local data files (if needed)

For campaign-specific data that doesn't fit in the library, create tests/UI/data/{domain}.ts in the core repo:

XML test data in tests/UI/data/xml/
TypeScript data-driven test arrays for forEach patterns

Rules

Conventions (no random data in assertions, deterministic Faker values) are in Playwright/CONTEXT.md. Skill-specific reminders:

Faker classes and predefined data live in the ui-testing-library, not the core repo
Faker defaults should produce valid entities — a bare new Faker{Domain}() must pass validation
Predefined data references demo install fixtures — don't assume entities exist that aren't in the standard install