-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Document requirements for running test-kitchen tests #25
Comments
For posterity, this is related to #20 (comment) The issue here is that the test case you were running spins up a node pool with 100 machines. From the docs:
So, in this case, As to resolution, I'm open to considering this a fixture setup issue (which should be thoroughly documented, to prevent it from happening to others), or to reducing the number of nodes that the test case in question expects to bring up, as 100 nodes is certainly not an average case. |
Can we simply document that requirement as the first step? |
@morgante I'm open to that iterative solution, but I think there's a larger conversation to be had here about repeatable testing. As we were talking about, we should probably focus on making sure that nobody has trouble running tests -- I'm of the belief that providing network fixtures is the least-bad way to handle this. EDIT: Addressing this here: #20 (comment) |
This was covered in #33. Closing. |
We need to document the requirements/dependencies for running tests with test-kitchen.
For reference, this is my current set of fixtures:
The text was updated successfully, but these errors were encountered: