Functional tests for the pipelines

Question

Functional tests for the pipelines

Closed this issue 2 years ago · 7 comments

Problem statement

There are no functional tests for the pipelines in the charts.

As a user of the helm charts, I would like to have automated tests that ensure that the pipelines deployed by the charts are and remain functional, so that I can have confidence that they will work when installed.

High-level Goals

There should be functional tests available for the pipelines in the repo.

Proposal description

Alternatives

No functional testing.

Additional context

At this time, there is a GitHub Actions workflow that uses the chart-testing tool to lint and test that the chart installs correctly. However, it does not perform any kind of functional test, other than ensuring that a helm install will succeed and the related pods (e.g. the event listener) start up correctly.

Acceptance Criteria

there are a set of tests defined that verify a minimum of functionality for the pipelines
tests are run on every PR to ensure that these functional tests pass

Answer 1 · 2022-02-07T13:59:05.000Z

Examplesof what could/should be avoided thanks to the tests are (parts of) #28 and #29: the fact that freshly installed charts come with references to non-existing trigger templates or bindings

Answer 2 · 2022-03-23T09:49:08.000Z

/triage accepted
/priority important-soon

Answer 3 · 2022-03-23T22:21:15.000Z

/sig devsecops

Answer 4 · 2022-06-22T01:02:09.000Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

Answer 5 · 2022-07-22T03:51:44.000Z

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

Answer 6 · 2022-08-21T06:47:08.000Z

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Answer 7 · 2022-08-21T06:47:10.000Z

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.