Open
Conversation
Member
|
We are looking to move client tests to our smoker library, starting with theforeman/smoker#11 -- give that a look and see if it might be a better place for the tests you want to introduce? |
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
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.
Hello
For this, my first, BATS test I need environment variables on the client to set Satellite and Capsule name.
I could not get Ansible "environment:" method to work., so tired creating them in an "BATS session. Then I found that each BATS @test block starts a new BASH shell, so any environment variables created in an earlier @test session are not present in the next @test session.
So then I put the variables in the ".bash_profile", fixed the FQDNs using Ansible, and then sourced the ".bash_profile" in each @test
Is that an acceptable method?