Re-organize description of record modes.

myronmarston · Feb 10, 2011 · f840dc3 · f840dc3
1 parent 9498ca2
commit f840dc3
Show file tree

Hide file tree

Showing 3 changed files with 16 additions and 6 deletions.
diff --git a/features/record_modes/all.feature b/features/record_modes/all.feature
@@ -1,7 +1,9 @@
 Feature: :all
 
-  The `:all` record mode records all requests and does not
-  replay any previously recorded responds.
+  The `:all` record mode will:
+
+    - Record new interactions.
+    - Never replay previously recorded interactions.
 
   This can be temporarily used to force VCR to re-record
   a cassette (i.e. to ensure the responses are not out of date)

diff --git a/features/record_modes/new_episodes.feature b/features/record_modes/new_episodes.feature
@@ -1,7 +1,13 @@
 Feature: :new_episodes
 
-  The `:new_episodes` record mode replays previously recorded
-  requests and records new ones.
+  The `:new_episodes` record mode will:
+
+    - Record new interactions.
+    - Replay previously recorded interactions.
+
+  It is similar to the `:once` record mode, but will _always_ record new
+  interactions, even if you have an existing recorded one that is similar
+  (but not identical, based on the `:match_request_on` option).
 
   Background:
     Given a file named "setup.rb" with:

diff --git a/features/record_modes/none.feature b/features/record_modes/none.feature
@@ -1,7 +1,9 @@
 Feature: :none
 
-  The `:none` record mode allows previously recorded responses
-  to be replayed, but raises an error for any new requests.
+  The `:none` record mode will:
+
+    - Replay previously recorded interactions.
+    - Cause an error to be raised for any new requests.
 
   This is useful when your code makes potentially dangerous
   HTTP requests.  The `:none` record mode guarantees that no