Skip to content
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

Where to go next? #2

Open
cmarzullo opened this issue Oct 15, 2016 · 5 comments
Open

Where to go next? #2

cmarzullo opened this issue Oct 15, 2016 · 5 comments

Comments

@cmarzullo
Copy link
Owner

I've been pretty happy with this utility so far. I know there's several different groups using this, so I wanted to create an issue about ideas.

One thing that could be added was better kitchen examples. One thing that took a little digging was figuring out how to do shared tests.

What else?

@nvtkaszpir
Copy link

Optionally allow to replace serverspec with github/chef/inspec?

@lowks
Copy link

lowks commented Oct 16, 2016

goss ?

@nvtkaszpir
Copy link

goss is in golang, from python world there is testinfra - yet both are not integrated with test-kitchen AFAIR.

@cmarzullo
Copy link
Owner Author

I can't say I've spent any time in go. Test infra is something I'd be pretty interested in. I know the team I'm in 'dislikes' having to do ruby in serverspec. Even though it's barely ruby.

I'm thinking that there should be a way to generate tests for the 'most common' test-kitchen supported verifiers.

Which kinda leads me to think there should be support for generating a formula without any verifier.
Which then makes me think that having to do a argument flag every time would be a pain in the arse. So maybe support for a .saltscaffoldrc type thing where you could do your settings.

@nvtkaszpir
Copy link

maybe extend https://hubblestack.io/ then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants