e2e-testing

Build and run deterministic E2E test images for InsForge changes.

12.7k|1.1k|Updated Jul 29, 2025
One-click install
npx skills add https://github.com/InsForge/InsForge --skill e2e-testing-insforge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/InsForge/InsForge/tree/main/.agents/skills/insforge-dev/e2e-testing
Command: npx skills add https://github.com/InsForge/InsForge --skill e2e-testing-insforge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the release-quality E2E testing for InsForge changes, ensuring that all deterministic tests pass before an OSS PR is submitted.

Core Features & Use Cases

  • Automated E2E Testing: Executes a set of deterministic E2E tests against InsForge changes.
  • Build and Test Image Tagging: Constructs and tags test images based on InsForge package.json versioning.
  • Deterministic Fixture Coverage Analysis: Checks for changes in deterministic fixture coverage due to InsForge changes.
  • Integration with GitHub Actions: Uses GitHub Actions workflows for building and testing.

Quick Start

Run the e2e-testing skill after local implementation and pre-PR checks to ensure the quality of InsForge changes.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema
How do I automate end-to-end testing for OSS pull requests?

Automated end-to-end testing for OSS pull requests is handled by building and running deterministic test images against your changes. This Skill integrates with GitHub Actions workflows to ensure all tests pass before submission.

What's the best way to tag test images for deterministic E2E testing?

The best way to tag test images for deterministic E2E testing is using versioning from your project's package.json. This ensures accurate tracking and reproducible test builds during release management.

Does this E2E testing workflow integrate with GitHub Actions?

Yes, this E2E testing workflow integrates directly with GitHub Actions. It uses GitHub Actions workflows to automate the building and testing processes for your changes.

How do I check deterministic fixture coverage before submitting a PR?

You can check deterministic fixture coverage by running the Skill after local implementation. It analyzes your changes to detect any shifts in fixture coverage prior to pre-PR checks.

When do I need to run deterministic E2E tests in the release management process?

Deterministic E2E tests should be run after local implementation and during pre-PR checks. This ensures release quality by verifying that all changes pass before an OSS PR is submitted.

Can I use this for release management of InsForge OSS changes?

Yes, you can use this for release management of InsForge OSS changes. It automates release-quality E2E testing to verify that all deterministic tests pass before submission.