kudobuilder / kudobuilder/kuttl

Assert at End of TestSuite Setup (Before Tests)

Open
#63 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
824
Forks
103
Avg merge
1d 11h
Merged PRs (30d)
6

Description

A great strategy for "ensuring" a controller or resources is to have a step 0 assert of that instance running
see https://github.com/kudobuilder/kudo/pull/1473
test/e2e/cli-install-uninstall/00-assert.yaml
```
apiVersion: v1
kind: Pod
metadata:
labels:
app: kudo-manager
control-plane: controller-manager
namespace: kudo-system
status:
phase: Running
```

Assuming you may want this as a precondition on all tests... it would be great to assert this at the end of TestSuite setup prior to tests.

Contributor guide

Open the contributing guide

Research direction

Start with the TestSuite setup path and compare it with test/e2e/cli-install-uninstall/00-assert.yaml and the linked KUDO pull request. Add a precondition check at the end of setup so the specified resource is verified before tests begin; done means the setup assertion runs for the relevant suites.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
testing
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.