e2e-auth-tests

Automate Cypress end-to-end test organization and execution for SchemaVaults Auth.

1|Updated Nov 5, 2025
One-click install
npx skills add https://github.com/schemavaults/auth --skill e2e-auth-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-auth-tests
Source: https://github.com/schemavaults/auth/tree/main/.claude/skills/e2e-auth-tests
Command: npx skills add https://github.com/schemavaults/auth --skill e2e-auth-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the organization and execution of Cypress-based end-to-end tests for the SchemaVaults Auth platform across local development and CI.

Core Features & Use Cases

  • Dynamic suite discovery: Tests are discovered automatically from the filesystem under tests/e2e-auth-tests/cypress/e2e/.
  • CI integration: Workflows run-e2e-tests.yml and run-e2e-test-suite.yml orchestrate per-suite jobs and artifact handling.
  • Helper commands: Custom Cypress commands streamline common setup like login, user creation, and resource seeding.

Quick Start

List available suites with bun run cli suites.

Frequently Asked Questions about e2e-auth-tests

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

FAQPage Schema
How do I automate Cypress E2E tests for authentication workflows in CI?

Automating Cypress E2E tests for auth workflows involves dynamic suite discovery from the filesystem and per-suite orchestration via YAML workflow files. This organizes execution into individual CI jobs for structured test runs and artifact handling.

What is dynamic test suite discovery in Cypress and how does it work?

Dynamic test suite discovery in Cypress automatically detects available test suites by scanning the filesystem under designated e2e directories. This removes manual configuration by mapping discovered files directly to executable test suites for orchestration.

Do I need Bun to run Cypress end-to-end test suites locally?

Yes, you need Bun installed alongside Cypress to run the end-to-end test suites locally. The workflow uses Bun to execute CLI commands that list available suites and manage the per-suite test orchestration process.

How do I handle superuser pre-registration and login setup in Cypress auth tests?

Handle superuser pre-registration and login setup by leveraging integration hooks and custom Cypress commands. These helper commands streamline common setup requirements like user creation, authentication login, and resource seeding for E2E tests.

Can I run individual Cypress auth test suites separately in a CI pipeline?

Yes, you can run individual Cypress auth test suites separately in CI by using a per-suite executor workflow. This executor dynamically discovers suites and triggers dedicated jobs for each suite, managing artifacts independently across the pipeline.

What are the limitations of orchestrating Cypress E2E tests dynamically from the filesystem?

A limitation of orchestrating Cypress E2E tests dynamically from the filesystem is strict directory dependency. Test suites must reside under the designated e2e path to be discovered, and both Cypress and Bun must be configured in the execution environment.