From 764d4d835bfea48c4200a929a7eddfaea1e5b0d2 Mon Sep 17 00:00:00 2001 From: Matthew Turland Date: Mon, 31 Aug 2015 21:58:51 -0500 Subject: [PATCH] Fix broken link in Getting Started section The link points to 06-UnitTests when it should point to 05-UnitTests. --- docs/02-GettingStarted.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/02-GettingStarted.md b/docs/02-GettingStarted.md index 621fdb4ea..3008d33ee 100644 --- a/docs/02-GettingStarted.md +++ b/docs/02-GettingStarted.md @@ -155,7 +155,7 @@ Each suite has its own bootstrap file. It's located in the suite directory and i ## Cept, Cest and Test Formats -Codeception supports three test formats. Beside the previously described scenario-based Cept format, Codeception can also execute [PHPUnit test files for unit testing](http://codeception.com/docs/06-UnitTests), and Cest format. +Codeception supports three test formats. Beside the previously described scenario-based Cept format, Codeception can also execute [PHPUnit test files for unit testing](http://codeception.com/docs/05-UnitTests), and Cest format. Cest combines scenario-driven test approach with OOP design. In case you want to group a few testing scenarios into one you should consider using Cest format. In the example below we are testing CRUD actions within a single file but with a several test (one per each operation): @@ -312,4 +312,4 @@ We took a look into the Codeception structure. Most of the things you need were * **Next Chapter: [AcceptanceTests >](/docs/03-AcceptanceTests)** -* **Previous Chapter: [< Introduction](/docs/01-Introduction)** \ No newline at end of file +* **Previous Chapter: [< Introduction](/docs/01-Introduction)**