Multiple stage status or ignore status
- Dominant language
- Go
- Stars
- 21
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
## Summary
Original Author: @dkirillov
It would be great to have a way to specify either multiple expected stage statuses or a way to ignore the stage status in an E2E test assertion.
This can be handy when dealing with stages that are influenced by external factors.
## Motivation
We have a lot of terraform plan, terraform apply (skippable) and terraform output modules.
The apply can either succeed or be skipped; depending on the changes in the terraform module. We have to retry it all the time because of this.
## Describe alternatives you've considered
## Additional context
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by locating the E2E assertion handling for stage status, then review how Terraform plan, apply, and output modules report status; define how multiple expected statuses or an ignored status should be specified, and add coverage showing both successful and skipped apply cases are accepted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, terraform
- Domain
- devops, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100