E2e Testing
Use this skill when an InsForge maintainer has finished an OSS repo change and is ready...
Install
npx skills add InsForge/InsForge --skill e2e-testing -g -a claude-code -y- Repository
- InsForge/InsForge13.3k
- Category
- Testing
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Lightabout 1,408 tokens
- Runs scripts
- No, instructions only
What it does
Use this skill when an InsForge maintainer has finished an OSS repo change and is ready to open, update, or submit the InsForge PR. Runs the release-quality deterministic E2E gate by building a package.json-derived InsForge test image tag, deciding whether sibling agent-e2e fixture coverage must change, dispatching the Deterministic Fixture E2E workflow, waiting for results, and triaging failures before PR submission.
InsForge E2E Testing Gate
Use this skill after local implementation and normal InsForge pre-PR checks pass, and before opening, updating, or submitting the InsForge OSS PR.
This is an additional release-quality gate. It does not replace local typecheck, lint, test, or build validation from the parent insforge-dev skill.
Repositories
- InsForge OSS repo: current workspace.
- E2E repo: remote GitHub repository
InsForge/agent-e2e.
Use the remote InsForge/agent-e2e repository for workflow dispatch and read-only workflow checks. Do not rely on a developer-specific local checkout path. Create or use a local checkout only when the deterministic fixture tests must be edited.
Build The Test Tag
- Read the root InsForge
package.jsonversion. - Increment only the patch number.
- Build a tag in this form:
v<major>.<minor>.<patch+1>-<feature-or-issue-slug>
Example: root version 2.2.3 and feature storage returning rls becomes v2.2.4-storage-returning-rls.
Use the package.json version as the only source of truth for the base version. Ignore higher existing test tags when calculating the base version.
Slug rules:
- Prefer the issue key, PR topic, or branch topic.
- Lowercase all letters.
- Replace runs of non-alphanumeric characters with one hyphen.
- Trim leading and trailing hyphens.
- Keep it short enough to scan in GitHub Actions and image tags.
Build The InsForge Image
Dispatch the InsForge Build and Push Docker Image workflow with the test tag:
gh workflow run "Build and Push Docker Image" --repo InsForge/InsForge --ref <insforge-feature-branch> -f test_tag=<test-tag>
Then wait for the matching run to complete:
gh run list --repo InsForge/InsForge --workflow "Build and Push Docker Image" --limit 10
gh run watch --repo InsForge/InsForge <run-id>
Do not start the cross-repo E2E workflow until the image build succeeds.
