メニュー
Run unit tests, integration tests, and e2e tests for the notification-service controller. Use when the user asks to run tests, debug test failures, or wants to know how to execute a specific test.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/konflux-ci/notification-service --skill run-testsコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Debug a running instance of the notification-service controller. Use when investigating why notifications are not being sent, PipelineRuns are stuck with finalizers, or the controller pod is unhealthy.
Set up a local development environment to run and test the notification-service controller against a real Kubernetes cluster. Use when the user wants to deploy the controller locally, manually test PipelineRun reconciliation, or iterate on changes.
| name | run-tests |
| description | Run unit tests, integration tests, and e2e tests for the notification-service controller. Use when the user asks to run tests, debug test failures, or wants to know how to execute a specific test. |
make test
This target chains manifests, generate, fmt, vet, and envtest before running:
KUBEBUILDER_ASSETS="$(setup-envtest use 1.30.x ...)" go test $(go list ./... | grep -v /e2e) -coverprofile cover.out
setup-envtest downloads kubebuilder binaries (kube-apiserver, etcd) to bin/k8s/1.30.0-<os>-<arch>internal/controller/ use envtest to spin up a real kube-apiserver + etcdtektoncd/pipeline module's config directory (resolved via operator-toolkit/test.GetRelativeDependencyPath)BeforeEach/AfterEach lifecycle)# Focus on a specific Ginkgo test by description
go test ./internal/controller/ -run TestControllers -v -- -ginkgo.focus "should add finalizer"
The pkg/notifier/ package uses standard Go testing (not Ginkgo):
go test ./pkg/notifier/ -v
| Symptom | Cause | Fix |
|---|---|---|
failed to start control plane | Missing kubebuilder binaries | Run make envtest or delete bin/k8s/ and re-run make test |
| GCS 401 downloading envtest assets | Exact version not found | Already mitigated by using wildcard 1.30.x in ENVTEST_K8S_VERSION |
CRDDirectoryPaths not found | GOPATH/pkg/mod missing tektoncd/pipeline | Run go mod download |
| Reflector watch errors | Cache race | The test suite disables cache for PipelineRun objects to avoid this |
make test-e2e
Runs go test ./test/e2e/ -v -ginkgo.v against whatever cluster your kubeconfig points to.
Important: The e2e suite is Kubebuilder scaffold and is not run in CI. The make install
step inside the test references config/crd/ which does not exist in this repo (this project
doesn't own a CRD). The e2e tests may need modification to work end-to-end.
For manual deployment testing on a real cluster, see the local-dev-setup skill.
make lint
Runs golangci-lint with a 5-minute timeout. The ginkgolinter rule is enabled and will fail on non-idiomatic Ginkgo/Gomega assertions.
After make test, coverage is written to cover.out. View it with:
go tool cover -html=cover.out