Permalink
Browse files

Update docs

  • Loading branch information...
1 parent 0229737 commit 7392b4f7e06adf2fdb470a15ba179cee51c57cae @bebraw committed Nov 15, 2011
Showing with 3 additions and 2 deletions.
  1. +2 −1 INSTALL
  2. +1 −1 README.md
View
@@ -1,3 +1,4 @@
Just run setup.py ("python setup.py install"). In case you use a *nix platform, you might need to use sudo.
-After the installation has been done properly you should have access to "speccer" command. Just run "speccer" ("run\_specs" in dev version) and it will seek for spec files in the current directory and run them if found. Try to navigate to the main project folder (speccer) or demo and run the command there for some results. Run "speccer -h" for some extra info.
+After the installation has been done properly you should have access to "run\_specs" command. Just run it to seek for spec files in the current directory and run them if found. Try to navigate to the main project folder (speccer) or demo and run the command there for some results. Invoke "run\_specs -h" for some extra info.
+
View
@@ -2,7 +2,7 @@
Speccer provides simple means to test individual modules. It uses a minimal, assert-free syntax. This syntax is compiled to actual code utilizing Python's unittest. Henceforth Speccer may be seen as an alternative to it in various situations.
-Run "setup.py install" to start rocking. See "demo" folder for an actual example. Once you have installed the tool just invoke "speccer" (run\_specs in dev version) at that directory. You should see some test results. Feel free to tweak the files to give it a proper go.
+Run "setup.py install" to start rocking. See "demo" folder for an actual example. Once you have installed the tool just invoke "run\_specs" at that directory. You should see some test results. Feel free to tweak the files to give it a proper go.
## Basic Specification Syntax

0 comments on commit 7392b4f

Please sign in to comment.