-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: use ephemeral workspaces in tests #219
Conversation
Conflicts with 'nonamedreturns' linter, and named returns isn't always used or recommended.
Adds two helpers to create random values and random workspaces to be used as ephemeral resources.
58b8093
to
ed98acf
Compare
Uses the new ephemeral workspace helpers to create the new, random workspace.
c39ac79
to
f621e00
Compare
f621e00
to
53f1fe0
Compare
Needed to set '10' as a constant to work around the 'mnd' linter.
53f1fe0
to
9b8545a
Compare
0144114
to
8941ce9
Compare
8941ce9
to
78ca434
Compare
78ca434
to
6dc37d4
Compare
@parkedwards - I got the ball rolling here and will pick it back up after the move 👍🏼 |
awesome - thank you @mitchnielsen |
func NewRandomPrefixedString() string { | ||
return TestAccPrefix + acctest.RandStringFromCharSet(RandomStringLength, acctest.CharSetAlphaNum) | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
…t into ephemeral-workspaces-in-tests
…t into ephemeral-workspaces-in-tests
@parkedwards - after some thinking, I wonder if it's nicer to just merge this one before it gets too big. Instead of doing it all in one big change, we can use this one to add the new helpers and implement it in a few places, and then I'll follow up with further implementation in separate PR(s). If you disagree just lmk and I'm happy to continue with making the changes here 👍🏼 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for getting the ball rolling on this dude, i know it can be a little tedious. but this is already a much needed improvement to the test suite
totally reasonable to me - we could also do something like "if you touch some code, update the tests" |
No worries at all, it's helped me get up to speed on how all of this works together 👍🏼 |
Summary
Related to #218
To do