Smoke Tests in CI #113
Merged
Smoke Tests in CI #113
Conversation
This file contains 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
added 30 commits
February 13, 2024 08:43
added 13 commits
February 23, 2024 11:49
added 9 commits
March 4, 2024 10:11
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds a job to run the smoke tests in Github Actions. The setup reuses the local
scripts/init.shandflake.nixfor the e2e setup. Thestart-services.shscript runs in the background. I added a http endpoint to the beacon relayer, to query whether the testnet is up. Once the testnet is up, the smoke tests are run. For now, I am just running the most important tests:Resolves: SNO-857
Snowbridge companion: Snowfork/snowbridge#1144