[DRE-commits] [test-kitchen] 13/39: Update man page

Hleb Valoshka tsfgnu-guest at moszumanska.debian.org
Fri Aug 5 12:46:50 UTC 2016


This is an automated email from the git hooks/post-receive script.

tsfgnu-guest pushed a commit to branch master
in repository test-kitchen.

commit ff1ac3d8ad4a1f44e08faf72968e924f562444a9
Author: Hleb Valoshka <375gnu at gmail.com>
Date:   Wed Jul 8 11:27:26 2015 +0300

    Update man page
---
 debian/kitchen.1 | 21 ++++++++++++++++++++-
 1 file changed, 20 insertions(+), 1 deletion(-)

diff --git a/debian/kitchen.1 b/debian/kitchen.1
index f2b990f..1d54459 100644
--- a/debian/kitchen.1
+++ b/debian/kitchen.1
@@ -1,8 +1,21 @@
 .\" DO NOT MODIFY THIS FILE!  It was generated by help2man 1.46.4.
 .TH KITCHEN "1" "June 2015" "Test Kitchen version 1.4.1" "User Commands"
 .SH NAME
-Kitchen \- Test Kitchen is a test harness tool to execute your configured code on one or more platforms in isolation
+Kitchen \- integration tool for Chef
 .SH DESCRIPTION
+Test Kitchen is a test harness tool to execute your configured code on one or
+more platforms in isolation. A driver plugin architecture is used which lets
+you run your code on various cloud providers and virtualization technologies
+such as Amazon EC2, Blue Box, CloudStack, Digital Ocean, Rackspace, OpenStack,
+Vagrant, Docker, LXC containers, and more. Many testing frameworks are already
+supported out of the box including Bats, shUnit2, RSpec, Serverspec, with
+others being created weekly.
+
+For Chef workflows, cookbook dependency resolver tools such as Berkshelf and
+Librarian-Chef are supported or you can simply have a cookbooks/ directory and
+Test Kitchen will know what to do. Support for Test Kitchen is already included
+in many Chef community cookbooks such as the MySQL, nginx, Chef Server, and
+runit cookbooks.
 .SS "Commands:"
 .TP
 kitchen console
@@ -40,6 +53,12 @@ kitchen help [COMMAND]
 .TP
 kitchen init
 # Adds some configuration to your cookbook so Kitchen can rock
+
+A `.kitchen.yml` will be created in your project base directory. This file
+describes your testing configuration; what you want to test and on which target
+platforms. Each of these suite and platform combinations are called instances.
+By default your instances will be converged with Chef Solo and run in Vagrant
+virtual machines.
 .TP
 kitchen list [INSTANCE|REGEXP|all]
 # Lists one or more instances

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-ruby-extras/test-kitchen.git



More information about the Pkg-ruby-extras-commits mailing list