e2e-test

Automate end-to-end plugin testing for Deenruv projects with Vitest.

11|1|Updated Oct 4, 2024
One-click install
npx skills add https://github.com/aexol-studio/deenruv --skill e2e-test-aexol-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-test
Source: https://github.com/aexol-studio/deenruv/tree/main/.opencode/skills/e2e-test
Command: npx skills add https://github.com/aexol-studio/deenruv --skill e2e-test-aexol-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

E2E testing for Deenruv plugins ensures reliable integration validation across the admin and shop interfaces, catching regressions before release.

Core Features & Use Cases

  • Bootstrap a full end-to-end test environment with Vitest and @deenruv/testing utilities.
  • Organize tests under plugins/<feature>-plugin/e2e/ with fixtures, shared configs, and generated types.
  • Validate plugin behavior in admin and shop APIs and ensure deterministic ports via test configuration.

Quick Start

Create an e2e test in your plugin's e2e/ directory and run pnpm e2e to execute it.

Frequently Asked Questions about e2e-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write E2E tests for Deenruv plugins using Vitest?

To start E2E testing, create a test file in your plugin's e2e/ directory and run the pnpm e2e command. This executes your tests using the bootstrapped environment and shared Vitest configuration to validate plugin behavior.

What is the required directory structure for Deenruv plugin E2E testing?

Deenruv plugin E2E testing requires organizing tests under plugins/<feature>-plugin/e2e/ with fixtures, shared configs, and generated types. This structure ensures deterministic tests across admin and shop APIs using Vitest.

Do I need a test environment bootstrap for Deenruv E2E tests?

Yes, a test environment bootstrap is required for Deenruv E2E tests. It establishes the shared Vitest configuration and structured e2e data and fixtures necessary to execute deterministic tests across admin and shop APIs.

Can I validate both admin and shop APIs in Deenruv plugin E2E tests?

Yes, you can validate both admin and shop APIs in Deenruv plugin E2E tests. Using Vitest and @deenruv/testing utilities, the tests ensure reliable integration validation and catch regressions across both interfaces before release.

Why are my Deenruv E2E tests failing with port conflicts?

Deenruv E2E tests require deterministic ports configured via the test configuration. Ensure your test environment bootstrap applies the shared Vitest config correctly to allocate fixed ports and prevent conflicts during admin and shop API validation.