Merge pull request #99 from wp-cli/mention-behat-dl

Mention `behat -dl` as a useful way of seeing defined steps

Author: schlessera

README.md

@@ -52,7 +52,7 @@ WP-CLI `packages/local/` directory.
 	[--require_wp_cli=<version>]
 		Required WP-CLI version for the package.
 		---
-		default: >=1.1.0
+		default: ^1.1.0
 		---
 
 	[--skip-tests]
@@ -75,9 +75,9 @@ wp scaffold package-tests <dir> [--ci=<provider>] [--force]
 ~~~
 
 WP-CLI makes use of a Behat-based testing framework, which you should use
-too. Functional tests are an integral ingredient of highly-quality,
-maintainable commands. Behat is a great choice as a testing framework
-because:
+too. This command generates all of the files you need. Functional tests
+are an integral ingredient of high-quality, maintainable commands.
+Behat is a great choice as a testing framework because:
 
 * It’s easy to write new tests, which means they’ll actually get written.
 * The tests interface with your command in the same manner as your users
@@ -106,8 +106,16 @@ Functional tests typically follow this pattern:
 * **When** a user performs a specific action,
 * **Then** the end result should be X (and Y and Z).
 
-This command generates all of the files needed for you to write Behat
-tests for your own command. Specifically:
+View all defined Behat steps available for use with `behat -dl`:
+
+```
+Given /^an empty directory$/
+Given /^an empty cache/
+Given /^an? ([^\s]+) file:$/
+Given /^"([^"]+)" replaced with "([^"]+)" in the ([^\s]+) file$/
+```
+
+The files generated by this command include:
 
 * `.travis.yml` is the configuration file for Travis CI.
 * `bin/install-package-tests.sh` will configure your environment to run

src/ScaffoldPackageCommand.php

@@ -370,9 +370,9 @@ public function package_readme( $args, $assoc_args ) {
 	 * Generate files needed for writing Behat tests for your command.
 	 *
 	 * WP-CLI makes use of a Behat-based testing framework, which you should use
-	 * too. Functional tests are an integral ingredient of highly-quality,
-	 * maintainable commands. Behat is a great choice as a testing framework
-	 * because:
+	 * too. This command generates all of the files you need. Functional tests
+	 * are an integral ingredient of high-quality, maintainable commands.
+	 * Behat is a great choice as a testing framework because:
 	 *
 	 * * It’s easy to write new tests, which means they’ll actually get written.
 	 * * The tests interface with your command in the same manner as your users
@@ -401,8 +401,16 @@ public function package_readme( $args, $assoc_args ) {
 	 * * **When** a user performs a specific action,
 	 * * **Then** the end result should be X (and Y and Z).
 	 *
-	 * This command generates all of the files needed for you to write Behat
-	 * tests for your own command. Specifically:
+	 * View all defined Behat steps available for use with `behat -dl`:
+	 *
+	 * ```
+	 * Given /^an empty directory$/
+	 * Given /^an empty cache/
+	 * Given /^an? ([^\s]+) file:$/
+	 * Given /^"([^"]+)" replaced with "([^"]+)" in the ([^\s]+) file$/
+	 * ```
+	 *
+	 * The files generated by this command include:
 	 *
 	 * * `.travis.yml` is the configuration file for Travis CI.
 	 * * `bin/install-package-tests.sh` will configure your environment to run