run-acctests
Executes acceptance tests (testacc) for a specific resource or suite in the GA or beta provider and outputs verbose debug logs.
소스 정보
- 저장소
- GoogleCloudPlatform/magic-modules
- 최근 소스 활동
- 2026년 10월 22일 23:10
- 감지된 SKILL.md 언어
- 영어
- 스타
- 975
- 포크
- 2,573
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- run-acctests
- description
- Executes acceptance tests (testacc) for a specific resource or suite in the GA or beta provider and outputs verbose debug logs.
# `run-acctests`
> **Note to AI Agents:** You MUST read the YAML frontmatter above first. Only read the rest of this file if the `description` matches your current roadblock or required task.
## Prerequisites
* Know the provider (`beta` or `ga`), service (e.g. `compute`), and test name (e.g. `TestAccComputeInstance_basic`).
* The provider must be generated from your current changes (`generate-provider` with the same `VERSION`).
* PR CI only runs beta acceptance tests, so run GA locally whenever GA behavior matters.
## Execution Steps
### 1. Select the provider
```bash
VERSION="beta" # or "ga"
if [ "$VERSION" = "ga" ]; then
REPO=terraform-provider-google; PKG_DIR=google
else
REPO=terraform-provider-google-beta; PKG_DIR=google-beta
fi
cd "${GOPATH:-$HOME/go}/src/github.com/hashicorp/$REPO" && pwd
```
### 2. Run the test
List all `func TestAcc` functions in the target test file (`grep '^func TestAcc' <test_file>`) and explicitly run each relevant test. Stream `TF_LOG=DEBUG` output to a log file so failures can be parsed.
```bash
TF_LOG=DEBUG make testacc TEST=./$PKG_DIR/services/<SERVICE_NAME> TESTARGS='-run=<TEST_NAME>$$' > test_output_$VERSION.log 2>&1
```
`no tests to run` on GA usually means the test isn't generated for GA (still guarded or `min_version: beta`). That is a finding, not a pass.
### 3. Verification & Handoff
* If the test succeeds, return to your primary workflow.
* If the test fails, do **NOT** attempt a blind fix immediately. You MUST invoke the `parse-debug-logs` skill on the log file to understand the API failure before proposing a fix.
GitHub에서 보기