Ability to execute smoke tests as a PR check for Kuadrant Operator PRs
- Dominant language
- Python
- Stars
- 7
- Forks
- 29
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
## Overview
Add ability to execute smoke tests as a PR check for pull requests for Kuadrant Operator repository.
- The `smoke` make target has already been defined and can be used - if it proves not ideal it can be changed.
- This should be optional
- This will likely involve spinning up a Kind cluster
- This can fit into a GitHub action that would run on the PR that is generated during the release process
This would give us more confidence in a PR and would be particularly useful for release candidate PRs.
This was created due to Zullip discussion: [#Releasing > What fail in the process V1.2.0-rc1](https://kuadrant.zulipchat.com/#narrow/channel/493669-Releasing/topic/What.20fail.20in.20the.20process.20V1.2E2.2E0-rc1/with/511649998)
Contributor guide
Research direction
Start by inspecting the existing `smoke` make target and the repository's current GitHub Actions and release-related workflows. Determine how an optional PR check can provision a Kind cluster and run that target, including the PR generated during release. Done means the optional check runs and reports its smoke-test result for the relevant pull requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, kubernetes
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100