docs page added

Author: DavertMik

_layouts/default.html

@@ -33,10 +33,11 @@
     <div class="nav">
     <a href="/" ><img src="/images/logo.png" alt="Codeception"></a>
       <ul>
+        <li><a href="/docs">Docs</a></li>
         <li><a href="/blog">Blog</a>
         <li><a href="/qa">Q&A</a>
         <li><a href="/credits">Credits</a>
-        <li><a class="active" href="/install">GET IT NOW!</a>
+        <li><a class="active" href="/install">INSTALL</a>
       </li></ul>
   </div>
 

css/screen.css

@@ -0,0 +1,70 @@
+---
+layout: page
+title: Codeception Documentation
+---
+
+# Documentation
+
+## Guides
+
+Guides will walk you though the basic concepts of testing to the full understanding knowlegde of Codeception.
+Everything you want to know about Codeception can be found in Guides.
+
+* [Intruduction](/docs/01-Introduction) - all about testing: acceptance, unit, and functional tests explained.
+* [Getting Started](/docs/02-GettingStarted) - setting up and writing a first test with Codeception
+* [Modules](/docs/03-Modules) - understanding modules and helpers
+* [Acceptance Tests](/docs/04-AcceptanceTests) - writing Selenium and PhpBrowser accetance tests.
+* [Functional Tests](/docs/05-FunctionalTests) - writing functional tests for popular PHP frameworks.
+* [Unit Tests in Scenarios](/docs/06-UnitTestsScenarios) - unit testing in scenarios proof of concept.
+* [Unit Tests Practice](/docs/07-UnitTestsPractice) - practical approach to unit testing in scenario manner.
+* [Data](/docs/08-Data) - repopulation of database, cleaning up data, using fixtures, etc.
+
+## References
+
+References explains API of verious parts of Codeception. Look for them if you forgot something.
+
+* [Commands](/docs/reference/commands) - explains usage of Codecption console utility.
+* Configuration - explains basics of suites configuration.
+* [Xml Builder](/docs/reference/xmlbuilder) - building XMLs pragmatically.
+* [Stubs](/docs/reference/stubs) - cool stub builder explained.
+
+## Modules
+
+Modules are used to test various parts of your application. There are plenty of those and many should arrive in a future. 
+Choose the best module for your needs and see it's reference.
+
+### Testing Web Applications with Javascript
+
+* [Selenium](/docs/modules/Selenium) - use Selenium server to run tests in browser.
+* [Selenium2](/docs/modules/Selenium2)  - use Selenium server to run tests in browser.
+* [ZombieJS](/docs/modules/ZombieJS) - use Zombie.js backend to run tests without browser.
+
+### Testing Web Applications without Javascript
+
+* [PhpBrowser](/docs/modules/PhpBrowser) - emulates browser usage by fetching and parsing html pages.
+
+### Testing Inside PHP Frameworks
+
+* [Symfony2](/docs/modules/Symfony2) - wraper for [Symfony2](http://symfony.com) functional tests.
+* [Zend Framework](/docs/modules/Zend) - wraper for [ZF](http://framework.zend.com) functional test.
+* [symfony](/docs/modules/symfony) - wraper for [symfony 1.x](http://symfony-project.org) functional test
+* [Kohana](/docs/modules/Kohana) 
+* [Social Engine](/docs/module/SocialEngine) - ZF module adopted for SE
+
+### Unit Testing
+
+Basically you could use PHPUnit tests for unit testing. But Codeception scenario-driven unit tests are much powerful )
+
+* [Unit](/docs/modules/unit) - everything for unit testing.
+
+### API Testing
+
+* [REST](/docs/modules/REST) - testing REST Web services (can be tested inside framework)
+* [SOAP](/docs/modules/SOAP) - testing SOAP WSDL web-services (can be tested inside framework)
+
+### Database Testing
+
+* [Db](/docs/modules/Db) - use to test changes in database
+* [Doctrine2](/docs/modules/doctrine2) - test database managed by [Doctrine2](http://www.doctrine-project.org/) ORM
+* [Doctrine](docs/modules/doctrine) - test database managed by [Doctrine](http://www.doctrine-project.org/) 1.x ORM
+

docs.markdown

@@ -0,0 +1,93 @@
+---
+layout: page
+title: Codeception Commands
+---
+
+# Commands
+
+Depending on version run Codeception console uitility in following way:
+
+* `php codecept.phar run` - for downloaded phar executable.
+* `codecept run` - for PEAR installation
+* `php vendor/bin/codecept` -  for composer installation.
+
+The commands listed below use PEAR installation as an example.
+
+## Run
+
+Executes Tests. 
+
+### Usage
+
+* `codecept run` - executes all tests in all suites
+* `codecept run suitename` - executes all test from this suite
+* `codecept run suitename testnameTest.php` - executes one test of this suite (provide local path for suite directory). 
+
+### Options
+
+* `--debug` - additional debug output will be printed.
+* `--steps` - all performed actions will be printed to console.
+* `--colors` - turn on colors (if disabled)
+* `--silent` - don't show the progress output.
+* `--report` - format results in report mode.
+* `--no-exit` - don't provide exit codes on finish. This option may be useful for using Codeception with some CI servers like Bamboo.
+* `--html` - generate html file with results. It will be stored as 'report.html' in tests/_log.
+* `--xml` - generate report in JUnit format for CI services. It will be stored as 'report.xml' in tests/_log.
+* `--tap` - generate report in TAP format. It will be stored as 'report.tap.log' in tests/_log.
+* `--json` - generate report in Json format. It will be stored as 'report.json' in tests/_log.
+
+## Boostrap
+
+Creates default config, tests directory and sample suites for current project.
+Use this command to start building a test suite.
+
+### Usage
+
+* `codecept bootstrap`
+
+## Install
+
+Tries to install Mink, PHPUnit, Symfony Components via PEAR. This command needs to successfully complete PEAR installation. This command may fail due to PEAR issues. We recommend to use phar executable or Composer, if you don't have time and enthusiasm to fight PEAR bugs.
+
+### Usage
+
+* `codecept install`
+
+## Generate Suite
+
+Generates a new empty suite. You may generate new suite for integration tests, for testing different part of appications, etc.
+
+### Usage
+
+* `codecept genrate:suite suitename guyname` - provide name of suite and name a Guy who will be used in tests.
+
+Don't create two guys with the same name!
+
+## Generate Cept
+
+Generates new empty test file for acceptance and functional tests. Scenario-based test is called Cept, though.
+
+### Usage
+
+* `codcept generate:cept suitename testname` - generates testnameCept.php inside the suite.
+* `codecept generate:cept suitename subdir/subdir/testnameCept.php` - generates file in subdir/subdir of suite dir.
+
+## Generate Cest
+
+Generates new empty test file for scenario-based unit tests. This file format is called Cest = Cept + Test.
+
+### Usage
+
+* `codcept generate:cest suitename testname` - generates testnameCest.php inside the suite.
+* `codecept generate:cest suitename subdir/subdir/testnameCest.php` - generates file in subdir/subdir of suite dir.
+
+## Generate Scenarios
+
+Generates text representation for all tests in suite. They are called scenarios and stored as a text files in the `log` dir.
+
+### Usage
+
+* `codecept generate:scenarios suitename` - generates for this suite.
+
+
+

docs/reference/commands.markdown

@@ -0,0 +1,54 @@
+---
+layout: page
+title: Codeception Stubs
+---
+
+# Stub
+
+Class for easily create stubs in your unit tests. You can use this class even inside PHPUnit tests too. It's a useful wrapper on top of PHPUnit mock builder.
+
+### Usage
+
+* `make` - creates new class bypassing constructor
+* `makeEmpty` - creates new class bypassing constructor with all methods return null.
+* `construct` - creates new class throgh constructor.
+* `constructEmpty` - creates new empty class throgh constructor with all methods return null.
+* `copy` - copies object and redefines it's properties.
+
+### Example 
+
+{% highlight php %}
+use \Codeception\Util\Stub as Stub;
+
+// create class instance with name set method 'save' redefined.
+$user = Stub::make('User', array('name' => 'davert', 'save' => function () { return true; }));
+
+// create class instance with all empty methods (will return NULL)
+$user = Stub::makeEmpty('User', array('getName' => function () { return 'davert'; }));
+$user->save(); // is empty and returns NULL
+$user->getName(); // return 'davert'
+
+// create class with empty methods except one
+$user = Stub::makeEmptyExcept('User', 'getName', array('name' => 'davert'));
+$user->save(); // is empty and returns NULL
+$user->getName(); // returns 'davert'
+
+// create class instance through constructor
+// second parameter is array, it's values will be passed to constructor.
+
+// similar to $user = new User($con, $is_new);
+$user = Stub::construct('User', array($con, $is_new), array('name' => 'davert'));
+
+// similar is constructEmpty 
+$user = Stub::constructEmpty('User', array($con, $is_new), array('getName' => function () { return 'davert'; }));
+
+// and constructEmptyExcept
+$user = Stub::constructEmptyExcept('User', 'getName', array($con, $is_new), array('name' => 'davert'));
+
+// copy and redefine class instance
+// can act with regular objects, not only stubs
+$user->getName(); // returns 'davert'
+$user2 = Stub::copy($user, array('name' => 'davert2'));
+$user->getName(); // returns 'davert2'
+{% endhighlight %}
+

docs/reference/stubs.markdown

@@ -0,0 +1,69 @@
+---
+layout: page
+title: Codeception Xml Builder
+---
+
+# Xml Builder
+
+That's a pretty simple yet powerful class to build XML structures in jQuery-like style. With no XML line actually written!
+Uses DOM extension to manipulate XML data.
+
+{% highlight php %}
+<?php
+
+$xml = new \Codeception\Util\XmlBuilder();
+$xml->users
+	->user
+		->val(1)
+		->email
+			->val('davert@mail.ua')
+			->attr('valid','true')
+			->parent()
+		->cart
+			->attr('empty','false')
+			->items
+				->item
+					->val('useful item');
+				->parents('user')
+		->active
+			->val(1);
+echo $xml;
+{% endhighlight %}
+
+This will produce this XML
+
+{% highlight xml %}
+
+<?xml version="1.0"?>
+<users>
+	<user>
+		1
+		<email valid="true">davert@mail.ua</email>
+		<cart empty="false">
+			<items>
+				<item>useful item</item>
+			</items>
+		</cart>
+		<active>1</active>
+	</user>
+</users>
+{% endhighlight %}
+
+Easy, right?
+
+### Usage
+
+Builder uses chained calls. So each call to builder returns a builder object. Except for `getDom` and `__toString` methods.
+
+* `$xml->node` - create new xml node and go inside of it. 
+* `$xml->node->val('value')` - sets the inner value of node
+* `$xml->attr('name','value')` - set the attribute of node
+* `$xml->parent()` - go back to parent node.
+* `$xml->parents('user')` - go back through all parents to `user` node.
+
+Export:
+
+* `$xml->getDom` - get a DOMDocument object
+* `$xml->__toString` - get a string representation of XML.
+
+[Source code](https://github.com/Codeception/Codeception/blob/master/src/Codeception/Util/XmlBuilder.php)