skills.rest
ray-manaloto
ray-manalotoOFFICIAL
Explore all skills by this author →
GitHub

mise-contrib-write-e2e-test

Enforce standardized conventions for writing jdx/mise end-to-end tests.

1|1|Updated Apr 8, 2026
Search Tags:#automation#bash#mise#e2e-testing#testing-conventions
One-click install
npx skills add https://github.com/ray-manaloto/claude-code-marketplace --skill mise-contrib-write-e2e-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mise-contrib-write-e2e-test
Source: https://github.com/ray-manaloto/claude-code-marketplace/tree/main/mise-toolkit/skills/mise-contrib-write-e2e-test
Command: npx skills add https://github.com/ray-manaloto/claude-code-marketplace --skill mise-contrib-write-e2e-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill defines a standardized approach for authoring and validating Bash-based end-to-end tests for jdx/mise, ensuring consistency and reliability across test suites.

Core Features & Use Cases

  • Provides layout templates for e2e tests (harness, assertion helpers, and test directories like cli/, backend/, config/).
  • Documents hard rules to prevent direct invocation, chmod misuse, and manual cleanup, enabling predictable CI behavior.
  • Supplies patterns for trust, environment setup, and isolated test lifecycles to improve test isolation and reproducibility.

Quick Start

Write your first e2e test following the laid-out layout and harness rules to ensure isolated, reproducible tests.

Frequently Asked Questions about mise-contrib-write-e2e-test

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

FAQPage Schema
How do I write reliable e2e tests for mise?▼

To write reliable mise e2e tests, you must follow a harness-driven workflow using an isolated MISE_DATA_DIR. This enforces strict non-interference policies and prevents direct invocation, ensuring predictable CI behavior across the e2e suite.

What layout should I use for bash e2e testing conventions?▼

Bash e2e testing conventions require a specific layout with dedicated directories for cli/, backend/, and config/, alongside assertion helpers. This structure provides reusable templates for reliable, isolated test lifecycles across the suite.

Why do my mise end-to-end tests fail in CI due to interference?▼

Mise e2e tests fail from interference when manual cleanup or chmod misuse violates strict non-interference policies. Enforcing a harness-driven workflow with an isolated MISE_DATA_DIR prevents these conflicts and ensures reproducible results.

Can I manually clean up test directories when automating bash e2e tests?▼

Manual cleanup is prohibited for bash e2e tests because it breaks predictable CI behavior. You must use the provided harness patterns to manage the isolated test lifecycle and maintain strict environment isolation.

Does writing jdx/mise e2e tests require a specific environment setup?▼

Writing jdx/mise e2e tests requires setting up an isolated MISE_DATA_DIR and establishing trust patterns. This environment setup is mandatory to achieve test isolation and reproducibility across the e2e suite.

Related Skills

Explore More Software Engineering Skills→
ray-manalotoray-manaloto
1

mise-contrib-overview

Document the jdx/mise codebase layout and build, test, and lint workflows.

Official
Advanced
usepowershellusepowershell
9

test-discipline

Update tests and assertion arrays when APIs or counted resources change.

Community
Basic
gmediagmedia
4

Refactor E2E Tests

Refactor E2E tests using shared factories to standardize module-level patterns.

Official
Advanced
salverius-techsalverius-tech

bash-testing

Test Bash and shell scripts using the Bats-core framework.

Community
Intermediate