Provider Test Patterns
hashicorp/agent-skills/terraform/provider-development/skills/provider-test-patterns
codingOfficial
Official Provider SkillView repo
Terraform provider acceptance test patterns using terraform-plugin-testing with the Plugin Framework. Covers test structure, TestCase/TestStep fields, ConfigStateChecks with custom statecheck.StateCheck implementations, plan checks, CompareValue for cross-step assertions, config helpers, import testing with ImportStateKind, sweepers, and scenario patterns (basic, update, disappears, validation, regression), and ephemeral resource testing with the echoprovider package. Use when writing, reviewing
Files4 files
SKILL.md415 lines
Loading editor…
Install
RecommendedOne command — your agent picks it up automatically.
Select an AI agent above to see the install command.
or
Manual Install
More stepsDownload the archive and add the files to your project manually.
Skill details
Versionv1.0.0
AuthorHashiCorp
Categorycoding
Skill IDhashicorp/agent-skills/terraform/provider-development/skills/provider-test-patterns
Files4 files
Related skills
Aws Ami BuilderBuild Amazon Machine Images (AMIs) with Packer using the amazon-ebs builder. Use when creating custom AMIs for EC2 instances.Azure Image BuilderBuild Azure managed images and Azure Compute Gallery images with Packer. Use when creating custom images for Azure VMs.Azure Verified ModulesAzure Verified Modules (AVM) requirements and best practices for developing certified Azure Terraform modules. Use when creating or reviewing Azure modules that need AVM certification.New Terraform ProviderUse this when scaffolding a new Terraform provider.Provider ActionsImplement Terraform Provider actions using the Plugin Framework. Use when developing imperative operations that execute at lifecycle events (before/after create, update, destroy).Provider DocsCreate, update, and review Terraform provider documentation for Terraform Registry using HashiCorp-recommended patterns, tfplugindocs templates, and schema descriptions. Use when adding or changing provider configuration, resources, data sources, ephemeral resources, list resources, functions, or guides; when validating generated docs; and when troubleshooting missing or incorrect Registry documentation.