Test swiftly release artifacts in a plain Linux environment #188
Conversation
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
Currently, there is no test coverage of a swiftly installation where there is no swift support at all, and nothing involving swiftly. Add a github workflow that performs a swiftly install using the release artifact. In order to facilitate this create an E2E test that performs these steps, but only in an environment where it can mutate the system. Also, make this test deployable to a plain Linux system with no swift support installed on it.
…to mimic zsh login shell
|
@swift-ci test macOS |
|
The approach taken here for bundling the tests to run in a plain environment doesn't really work on macOS. Next step is probably to make a CLT that runs swiftly E2E tests on a system that it can mutate. |
|
Closing this in favour of #296 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Currently, there is no test coverage of a swiftly installation where there is no swift support at all, and nothing involving swiftly. Add a github workflow that performs a fresh swiftly install using the released artifact, installs the latest available swift toolchain, and verifies that the shell environment has been updated.
In order to facilitate this create an E2E test that performs these steps, but only in an environment where it can mutate the system. Also, make this test deployable to a plain Linux system with no swift support installed on it so that the tests can be run.