Skip to content

Commit

Permalink
small typo fix
Browse files Browse the repository at this point in the history
  • Loading branch information
filler committed Dec 20, 2013
1 parent 8a5fe38 commit a34bd10
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/source/docs/getting-started/next-steps.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,6 @@ From here, there are a few resources that can help you along your infrastructure
* Write a blog post describing getting started with Test Kitchen, or an interesting problem Test Kitchen has allowed you to solve
* Take a look at the excellent O'Reilly book [Test-driven Infrastructure with Chef](http://shop.oreilly.com/product/0636920030973.do)

One question that users often raise is: "How can I get Test Kitchen to test multiple machines?". Usually this question really means: I want to test the interaction between machines, for example a webserver and a database. It's important to understand that this is not the kind of testing that Test Kitchen was designed for. Acceptance testing of infrastructure stacks is valueable, fascinating and difficult - for an approach which makes use of Test Kitchen as a library, see [Leibniz](http://leibniz.cc).
One question that users often raise is: "How can I get Test Kitchen to test multiple machines?". Usually this question really means: I want to test the interaction between machines, for example a webserver and a database. It's important to understand that this is not the kind of testing that Test Kitchen was designed for. Acceptance testing of infrastructure stacks is valuable, fascinating and difficult - for an approach which makes use of Test Kitchen as a library, see [Leibniz](http://leibniz.cc).

The rest of the documentation is a work in progress so bear with us. Better yet, if you've learned something and want to contribute, please **fork the docs**!

0 comments on commit a34bd10

Please sign in to comment.