=auto-updated documentation

Davert · Davert · commit 3aabb59c43e1 · 2013-01-16T01:12:05.000+02:00
diff --git a/docs/01-Introduction.markdown b/docs/01-Introduction.markdown
@@ -141,5 +141,5 @@ Despite the wide popularity of TDD, few PHP developers ever write automatic test
 It could be called a BDD framework. All Codeception tests are written in a descriptive manner. Just by looking in the test body you can get a clear understanding of what is being tested and how it is performed. Even complex tests with many assertions are written in a simple PHP DSL.
 
 
-*continue reading...*
+
 * **Next Chapter**: [GettingStarted](/docs/02-GettingStarted)
diff --git a/docs/02-GettingStarted.markdown b/docs/02-GettingStarted.markdown
@@ -324,6 +324,6 @@ There are plenty of useful Codeception commands.
 We took a look into the Codeception structure. Most of the things you need were already generated by the `bootstrap` command. After you have reviewed the basic concepts and configurations, you can start writing your first scenarios. 
 
 
-*continue reading...*
+
 * **Previous Chapter**: [Introduction](/docs/01-Introduction)
 * **Next Chapter**: [Modules](/docs/03-Modules)
diff --git a/docs/03-Modules.markdown b/docs/03-Modules.markdown
@@ -372,6 +372,6 @@ Fork the Codeception repository, put the module into the `src/Codeception/Module
 
 
 
-*continue reading...*
+
 * **Previous Chapter**: [GettingStarted](/docs/02-GettingStarted)
 * **Next Chapter**: [AcceptanceTests](/docs/04-AcceptanceTests)
diff --git a/docs/04-AcceptanceTests.markdown b/docs/04-AcceptanceTests.markdown
@@ -395,6 +395,6 @@ Writing acceptance tests with Codeception and PhpBrowser is a good start. You ca
 
 
 
-*continue reading...*
+
 * **Previous Chapter**: [Modules](/docs/03-Modules)
 * **Next Chapter**: [FunctionalTests](/docs/05-FunctionalTests)
diff --git a/docs/05-FunctionalTests.markdown b/docs/05-FunctionalTests.markdown
@@ -169,6 +169,6 @@ This makes your tests shorter and faster. In other cases, if you don't use frame
 If you are using a framework other than the ones listed here, create a module for it and share it with community.
 
 
-*continue reading...*
+
 * **Previous Chapter**: [AcceptanceTests](/docs/04-AcceptanceTests)
 * **Next Chapter**: [UnitTests-TEST](/docs/06-UnitTests-TEST)
diff --git a/docs/06-UnitTests-TEST.markdown b/docs/06-UnitTests-TEST.markdown
@@ -212,6 +212,6 @@ PHPUnit tests are very cool, but for complex tests you want to have more strict
 PHPUnit tests is a first-class citizen in test suites. Whenever you need to write and execute unit tests, you don't need to install PHPUnit manually, but use a Codeception to execute them. Some nice features are added to common unit tests by integrating Codeception modules. For most of unit and integration testing PHPUnit tests are just enough. They are fast and easy to maintain. But when you need some advanced features like mocking, use the special Cest format, described in next chapters.
 
 
-*continue reading...*
+
 * **Previous Chapter**: [FunctionalTests](/docs/05-FunctionalTests)
 * **Next Chapter**: [UnitTestsScenarios](/docs/07-UnitTestsScenarios)
diff --git a/docs/07-UnitTestsScenarios.markdown b/docs/07-UnitTestsScenarios.markdown
@@ -208,6 +208,6 @@ You are free to decide the testing framework you will use for unit tests. Codece
 Codeception provides you with a cool DSL to simplify your unit tests. You are writing the scenario definitions, not the actual executed code. Behind the scenes all the dirty work is done by Codeception. You write only the testing logic.
 
 
-*continue reading...*
+
 * **Previous Chapter**: [UnitTests-TEST](/docs/06-UnitTests-TEST)
 * **Next Chapter**: [UnitTests-CEST](/docs/08-UnitTests-CEST)
diff --git a/docs/08-UnitTests-CEST.markdown b/docs/08-UnitTests-CEST.markdown
@@ -325,6 +325,6 @@ If you don't use ORMs and MySQL, consider using SQLite for testing instead.
 Codeception has it's powers and it's limits. We believe Codeception's limitations keep your tests clean and narrative. Codeception makes writing bad code for tests more difficult. Codeception has simple but powerful tools to create stubs and mocks. Different modules can be attached to unit tests which, just for an example, will simplify database interactions. 
 
 
-*continue reading...*
+
 * **Previous Chapter**: [UnitTestsScenarios](/docs/07-UnitTestsScenarios)
 * **Next Chapter**: [Data](/docs/09-Data)
diff --git a/docs/09-Data.markdown b/docs/09-Data.markdown
@@ -248,6 +248,6 @@ To manipulate sample data in a test, use fixtures that can be defined within the
 
 
 
-*continue reading...*
+
 * **Previous Chapter**: [UnitTests-CEST](/docs/08-UnitTests-CEST)
 * **Next Chapter**: [WebServices](/docs/10-WebServices)
diff --git a/docs/10-WebServices.markdown b/docs/10-WebServices.markdown
@@ -207,6 +207,6 @@ class ApiHelper extends \Codeception\Module {
 Codeception has two modules that will help you to test various web services. They need a new `api` suite to be created. Remember, you are not limited to test only response body. By including Db module you may check if a user was created after the `CreateUser` call. You can improve testing scenarios by using REST or SOAP responses in your helper methods.
 
 
-*continue reading...*
+
 * **Previous Chapter**: [Data](/docs/09-Data)
 * **Next Chapter**: [Codecoverage](/docs/11-Codecoverage)
diff --git a/docs/11-Codecoverage.markdown b/docs/11-Codecoverage.markdown
@@ -137,5 +137,5 @@ you the most complete information on which parts of your applications are tested
 
 
 
-*continue reading...*
+
 * **Previous Chapter**: [WebServices](/docs/10-WebServices)
