Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Readme edit.

  • Loading branch information...
commit 7c3de5a9533df0ab6aff399a53bee39b01613bbb 1 parent 6f569c2
Martin Bilski authored
Showing with 12 additions and 11 deletions.
  1. +2 −1  .gitignore
  2. +10 −10 README.md
View
3  .gitignore
@@ -1 +1,2 @@
-spec/examples/tests.log
+spec/examples/tests.log
+spec/tests.log
View
20 README.md
@@ -38,6 +38,16 @@ The matcher is fairly flexible, supports regular expressions and also works with
More examples: [spec/examples/](https://github.com/bilus/rspec-cramp/tree/master/spec/examples)
+Project status
+--------------
+
+**IMPORTANT:** This is work in progress. I haven't created a gem yet.
+
+1. There are still pending specs I'll take care of soon (esp. passing extra headers).
+2. I extracted the code from one of my projects and wrote the matchers from scratch test-first. Still, after the weekend I plan to actually use it to replace the 'legacy' matchers in my project; this will probably uncover some bugs.
+
+If you have any comments regarding the code as it is now (I know it's a bit messy), please feel free to tweet [@MartinBilski](http://twitter.com/#!/MartinBilski)
+
Notes
----
@@ -74,13 +84,3 @@ Notes
end
In general, I recommend using the 'respond_with' matcher whenever possible; I think it makes the specs more readable because it hides some gory details (for good or bad).
-
-Project status
---------------
-
-*Important:* This is work in progress. I haven't created a gem yet.
-
-1. There are still pending specs I'll take care of soon (esp. passing extra headers).
-2. I extracted the code from one of my projects and wrote the matchers from scratch test-first. Still, after the weekend I plan to actually use it to replace the 'legacy' matchers in my project; this will probably uncover some bugs.
-
-If you have any comments regarding the code as it is now (I know it's a bit messy), please feel free to tweet [@MartinBilski](http://twitter.com/#!/MartinBilski)
Please sign in to comment.
Something went wrong with that request. Please try again.