concurrent-api-test-from-gherkin

You can convert Gherkin feature files into parallel API tests by mapping scenarios to vitest tests using the @villedemontreal/concurrent-api-tests library, ensuring each test runs concurrently with isolated data partitions defined in a data-partitions.yaml file.

Concurrent API tests fail from shared state when data partitions are not isolated. This skill enforces per-endpoint data partitioning using a data-partitions.yaml specification to ensure zero cross-test state and reliable parallel execution.

Yes, an OpenAPI specification is required alongside Gherkin feature files and a data-partitions.yaml to generate vitest-based concurrent API tests that validate endpoints with proper arrange-act-assert structure.

The best way to run isolated API tests in parallel is using stateless test design with per-endpoint data partitioning, mapping Gherkin scenario outlines to it.each blocks to ensure concurrent execution without cross-test dependencies.

Yes, Gherkin scenario outlines are mapped to it.each blocks in vitest, generating data-driven concurrent API tests that validate multiple examples against isolated data partitions defined in your data-partitions.yaml.

Gherkin scenario mapping translates feature files, rules, and examples into structured vitest describe and it blocks, applying arrange-act-assert patterns to generate concurrent API tests with isolated data partitions.