skills.rest
memorysaver
memorysaverCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

e2e-test

Automate end-to-end testing for PaperLens features with scripted gates, BDD journeys, and API drivers.

Updated May 18, 2026
Search Tags:#automated testing#end-to-end testing#BDD#API testing#PaperLens
One-click install
npx skills add https://github.com/memorysaver/project-understanding --skill e2e-test-memorysaver
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-test
Source: https://github.com/memorysaver/project-understanding/tree/main/skills/e2e-test
Command: npx skills add https://github.com/memorysaver/project-understanding --skill e2e-test-memorysaver

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bun, cypress, jest, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the end-to-end testing process for PaperLens features, including scripting gates, declarative BDD journeys, and API drivers. It helps ensure feature quality and reliability through automated testing.

Core Features & Use Cases

  • Scripted Gates: Run deterministic tests using 'bun test' to verify machinery and functional components.
  • Journey Dogfood: Execute declarative BDD-style user-story journeys to test the product with real model/providers and environments.
  • API Drivers: Verify backend state, bulk setup, and async flows using API calls.
  • Use Case: When adding a new feature to PaperLens, use this Skill to create and run tests to ensure the feature behaves as expected.

Quick Start

Run the full suite of end-to-end tests for the PaperLens feature 'new_feature'.

Frequently Asked Questions about e2e-test

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

FAQPage Schema
How do I automate end-to-end testing for new features?▼

Automating end-to-end testing involves running a structured pipeline with scripted gates, BDD journey definitions, and API drivers to verify feature behavior, backend state, and async flows. This pipeline handles test setup, execution, and reporting.

What is BDD-style journey testing and when do I need it?▼

BDD-style journey testing executes declarative user-story journeys to dogfood features with real model providers and environments. You need it to validate complex user interactions and verify that machinery components behave as expected.

How do I verify backend state and async flows during API testing?▼

Verifying backend state and async flows during API testing requires using API drivers to execute bulk setup and validate server responses. This ensures the backend infrastructure correctly supports the automated test pipeline.

Do I need bun to run automated testing pipelines with Cypress and Jest?▼

Yes, you need bun to run deterministic scripted gates using 'bun test'. While Cypress and Jest are included as dependencies for the environment, bun executes the core functional component verification.

What's the best way to structure an end-to-end test pipeline for feature quality?▼

The best way to structure an end-to-end test pipeline is to tier tests into deterministic scripted gates, declarative BDD journeys, and API drivers. This separation ensures comprehensive coverage of machinery, user flows, and backend state.

Related Skills

Explore More Software Engineering Skills→
hopeoverturehopeoverture

worldcrafter-test-generator

Generate unit, integration, and end-to-end tests with Vitest, real database integration, and Playwright.

Community
Advanced
FortiumPartnersFortiumPartners
11

ExUnit Test Framework

Generate and execute ExUnit tests from bug reports or feature descriptions.

Official
Advanced
willyu1007willyu1007

test-ci-gitlab-ci

Integrate automated web, API, mobile, and performance tests into GitLab CI/CD pipelines.

Community
Intermediate
kraftvaerkkraftvaerk

umbraco-testing

Route Umbraco backoffice extension testing to specialized skills by testing level.

Official
Intermediate