test: Add smoke test for run-integration-test action - #138
Merged
Conversation
Did I mention I hate beku?
Freaking beku man >:/
This ensures that the interaction between the run-integration-test and send-slack-notification action is always tested, even if the test succeeds (which should be basically always).
NickLarsenNZ
moved this from Development: Waiting for Review
to Development: In Review
in Stackable Engineering
Techassi
moved this from Development: In Review
to Development: Done
in Stackable Engineering
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #137.
This PR adds a workflow to smoke test the
run-integration-testaction similar to what we already do with many other actions in this repo.The
run-testsscript is annoying. It can probably be trimmed down a lot, but it is too cumbersome to fiddle around with it and its interaction with beku/kuttl. With bbq, this will be way more straight forward. Shared functionality can be implemented as reusable task lists which can be pulled in automatically via Git.