run-acceptance-tests▌
hashicorp/agent-skills · updated Apr 8, 2026
Execute and diagnose Go acceptance tests for Terraform providers with structured troubleshooting.
- ›Run focused acceptance tests using go test -run=TestAccFeatureHappyPath with TF_ACC=1 environment variable
- ›Diagnose failures progressively: retry with -count=1 , enable verbose output with -v , activate debug logging via TF_LOG=debug , and persist Terraform workspace with TF_ACC_WORKING_DIR_PERSIST=1
- ›Validate test reliability by intentionally breaking a TestCheckFunc, re-running the test
An acceptance test is a Go test function with the prefix TestAcc.
To run a focussed acceptance test named TestAccFeatureHappyPath:
-
Run
go test -run=TestAccFeatureHappyPathwith the following environment variables:TF_ACC=1
Default to non-verbose test output.
-
The acceptance tests may require additional environment variables for specific providers. If the test output indicates missing environment variables, then suggest how to set up these environment variables securely.
To diagnose a failing acceptance test, use these options, in order. These options are cumulative: each option includes all the options above it.
- Run the test again. Use the
-count=1option to ensure thatgo testdoes not use a cached result. - Offer verbose
go testoutput. Use the-voption. - Offer debug-level logging. Enable debug-level logging with the environment
variable
TF_LOG=debug. - Offer to persist the acceptance test's Terraform workspace. Enable
persistance with the environment variable
TF_ACC_WORKING_DIR_PERSIST=1.
A passing acceptance test may be a false negative. To "flip" a passing
acceptance test named TestAccFeatureHappyPath:
- Edit the value of one of the TestCheckFuncs in one of the TestSteps in the TestCase.
- Run the acceptance test. Expect the test to fail.
- If the test fails, then undo the edit and report a successful flip. Else, keep the edit and report an unsuccessful flip.
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★53 reviews- ★★★★★Mei Torres· Dec 28, 2024
run-acceptance-tests reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Dhruvi Jain· Dec 20, 2024
We added run-acceptance-tests from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Ama Rahman· Dec 4, 2024
I recommend run-acceptance-tests for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Kabir Harris· Nov 23, 2024
Useful defaults in run-acceptance-tests — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Luis Park· Nov 19, 2024
run-acceptance-tests has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Oshnikdeep· Nov 11, 2024
run-acceptance-tests fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Ira Gupta· Oct 14, 2024
run-acceptance-tests has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Kiara Anderson· Oct 10, 2024
Useful defaults in run-acceptance-tests — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Ganesh Mohane· Oct 2, 2024
run-acceptance-tests is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Aarav Dixit· Sep 25, 2024
Registry listing for run-acceptance-tests matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 53