You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems we have some convergent ideas. I'm more interested in ChefSpec passing since it's a lower barrier of entry than Vagrant and KitchenCI. Happy to collaborate -- let me know what you think.
Cheers,
Peter
The text was updated successfully, but these errors were encountered:
That looks pretty cool. I like that you've got a nice clean rake task that handles everything. I'm starting to move towards that approach myself - I've mostly been concerned with getting the basic framework down for others to hack against rather than write steps myself so far.
I think this is important because it presents students with a consistent testing / feedback mechanism (kitchen seemed like a good idea at commit zero but I'm definitely leaning more towards rake or thor now). The tools used to do the testing may vary from step to step, though. For the master branch I've tried to implement the same tests in a number of different frameworks as an example to both students and authors.
Meanwhile, step authors/maintainers are obviously responsible for using the most appropriate mechanism to test the concept they're teaching. I don't know how we'd test, say, chef-metal steps but I don't think we need to design for that quite yet!
Happy to give you commit bit if you want to hack on it.
https://github.com/pburkholder/chef-examples
Seems we have some convergent ideas. I'm more interested in ChefSpec passing since it's a lower barrier of entry than Vagrant and KitchenCI. Happy to collaborate -- let me know what you think.
Cheers,
Peter
The text was updated successfully, but these errors were encountered: