provider-test-speed

Parallelize Terraform provider acceptance tests into 4–5 groups with retries.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/hashi-demo-lab/terraform-provider-aap --skill provider-test-speed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: provider-test-speed
Source: https://github.com/hashi-demo-lab/terraform-provider-aap/tree/main/.claude/skills/provider-test-speed
Command: npx skills add https://github.com/hashi-demo-lab/terraform-provider-aap --skill provider-test-speed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill analyzes and optimizes Terraform provider acceptance test execution to maximize speed while ensuring a 100% pass rate, helping teams get faster feedback without sacrificing correctness.

Core Features & Use Cases

  • Parallel test grouping by resource type to avoid backend contention and balance load.
  • Pre-compile a single test binary and run groups with -test.* flags to minimize rebuilds and I/O.
  • Exponential backoff retries for transient failures and comprehensive logging of results.
  • Use case: you want to speed up large acceptance suites and quantify the speedup from parallelization.

Quick Start

Run the provider-test-speed workflow to generate a ready-to-run parallel test script and review its grouping strategy before execution.

Frequently Asked Questions about provider-test-speed

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

FAQPage Schema
How do I speed up Terraform provider acceptance test suites without causing failures?

Speed up Terraform provider acceptance test suites by grouping tests into 4–5 parallel execution groups based on resource type. This minimizes backend contention and balances load while maintaining a 100% pass rate.

What is the best way to parallelize Terraform acceptance tests?

Parallelize Terraform acceptance tests by pre-compiling a single test binary and running groups with -test.run, -test.count=1, -test.timeout, and -test.v flags to minimize rebuilds and I/O overhead.

How does pre-compiling the test binary improve Terraform provider test execution?

Pre-compiling the test binary improves Terraform provider test execution by building once instead of per run, minimizing rebuilds and I/O so parallel groups start faster and overall suite timing drops.

Can I run parallel Terraform provider tests safely without backend contention?

Run parallel Terraform provider tests safely by grouping tests across resource types to avoid backend contention, balancing load across 4–5 groups while validating performance improvements without sacrificing correctness.

What should I do when parallel Terraform provider tests time out or fail transiently?

Handle transient Terraform provider test timeouts by applying exponential backoff retries within the parallel execution workflow, logging results comprehensively to identify slow tests and quantify speedup.

How do I quantify speedup from parallelizing Terraform acceptance tests?

Quantify parallelization speedup by analyzing timing data from the workflow, which identifies slow tests, balances load across groups, and logs results to validate performance improvements against the original suite duration.