Skip to content

Conversation

@swadeley
Copy link

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?

@ehelms
Copy link
Member

ehelms commented Jan 22, 2021

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants