write-e2e-tests

Generates Terraform end-to-end test modules for AWS services using winterbaume.

15|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/moriyoshi/winterbaume --skill write-e2e-tests-moriyoshi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-e2e-tests
Source: https://github.com/moriyoshi/winterbaume/tree/main/.agents/skills/write-e2e-tests
Command: npx skills add https://github.com/moriyoshi/winterbaume --skill write-e2e-tests-moriyoshi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating Terraform end-to-end test modules for AWS services that exercise real terraform workflows against an in-process winterbaume server.

Core Features & Use Cases

  • Generates a complete Terraform E2E test module under tests/e2e/terraform/ for a specified AWS service.
  • Provides smoke-testing patterns and a ready-to-run harness to validate provider interactions.
  • Supports an isolated-server approach for services with SDK-validated updates to prevent cross-test contamination.

Quick Start

Provide the service name to generate and run the E2E Terraform tests against the in-process Winterbäume server.

Frequently Asked Questions about write-e2e-tests

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

FAQPage Schema
How do I generate Terraform E2E tests for AWS services?▼

To generate Terraform E2E tests for AWS services, provide the service name to create a ready-to-run module under tests/e2e/terraform. This module exercises real terraform workflows against an in-process winterbaume server using smoke-test patterns.

What is an isolated-server approach for Terraform E2E testing?▼

An isolated-server approach in Terraform E2E testing prevents cross-test contamination for services with SDK-validated updates. It separates server instances during test execution to ensure deterministic results when validating problematic provider interaction paths.

How do I run smoke tests against an in-process winterbaume server?▼

Running smoke tests against an in-process winterbaume server involves generating a Terraform E2E test harness that validates provider interactions. The generated module enforces deterministic naming and supports batch_apply test flows for immediate execution.

Does the generated Terraform E2E test harness support batch_apply workflows?▼

Yes, the generated Terraform E2E test harness supports batch_apply test flows. It enforces deterministic naming, validates hook points like provider endpoints, and integrates module structure testing within the tests/e2e/terraform directory.

Can I use this to test AWS services not supported by winterbaume crates?▼

No, you cannot test AWS services not supported by winterbaume crates. The E2E test generation applies specifically to services supported by winterbaume, exercising real terraform workflows against the in-process server to validate provider interactions.

What limitations exist when generating E2E tests for SDK-validated AWS service updates?▼

Generating E2E tests for SDK-validated AWS service updates presents cross-test contamination risks. The generator mitigates this by providing an isolated-server approach, ensuring deterministic naming and preventing state leakage between batch_apply test flows.