Adding "edit" link (Codeception#418)

ThomasLandauer · web-flow · commit 7c9ba03b46ab · 2021-01-03T02:08:36.000+02:00
* Adding "edit" link

* Update 03-AcceptanceTests.md

* Update 04-FunctionalTests.md

* Update 05-UnitTests.md

* Update 06-ModulesAndHelpers.md

* Update 07-AdvancedUsage.md

* Update 08-Customization.md

* Update 09-Data.md

* Update 10-APITesting.md

* Update 11-Codecoverage.md

* Update 12-ContinuousIntegration.md

* Update 12-ParallelExecution.md
diff --git a/docs/02-GettingStarted.md b/docs/02-GettingStarted.md
@@ -444,3 +444,6 @@ After you have reviewed the basic concepts and configurations, you can start wri
 
 * **Next Chapter: [AcceptanceTests >](/docs/03-AcceptanceTests)**
 * **Previous Chapter: [< Introduction](/docs/01-Introduction)**
+
+<p>&nbsp;</p>
+<div class="alert alert-warning"><a href="https://github.com/Codeception/codeception.github.com/edit/master/docs/02-GettingStarted.md"><strong>Edit</strong> this page on GitHub</a></div>
diff --git a/docs/03-AcceptanceTests.md b/docs/03-AcceptanceTests.md
@@ -899,3 +899,6 @@ If you need to access the database, you can use the [Db Module](http://codecepti
 
 * **Next Chapter: [FunctionalTests >](/docs/04-FunctionalTests)**
 * **Previous Chapter: [< GettingStarted](/docs/02-GettingStarted)**
+
+<p>&nbsp;</p>
+<div class="alert alert-warning"><a href="https://github.com/Codeception/codeception.github.com/edit/master/docs/03-AcceptanceTests.md"><strong>Edit</strong> this page on GitHub</a></div>
diff --git a/docs/04-FunctionalTests.md b/docs/04-FunctionalTests.md
@@ -281,3 +281,6 @@ If you are using a framework other than the ones listed here, create a module fo
 
 * **Next Chapter: [UnitTests >](/docs/05-UnitTests)**
 * **Previous Chapter: [< AcceptanceTests](/docs/03-AcceptanceTests)**
+
+<p>&nbsp;</p>
+<div class="alert alert-warning"><a href="https://github.com/Codeception/codeception.github.com/edit/master/docs/04-FunctionalTests.md"><strong>Edit</strong> this page on GitHub</a></div>
diff --git a/docs/05-UnitTests.md b/docs/05-UnitTests.md
@@ -525,4 +525,7 @@ For most unit and integration testing, PHPUnit tests are enough. They run fast,
 
 
 * **Next Chapter: [ModulesAndHelpers >](/docs/06-ModulesAndHelpers)**
-* **Previous Chapter: [< FunctionalTests](/docs/04-FunctionalTests)**
+* **Previous Chapter: [< FunctionalTests](/docs/04-FunctionalTests)**
+
+<p>&nbsp;</p>
+<div class="alert alert-warning"><a href="https://github.com/Codeception/codeception.github.com/edit/master/docs/05-UnitTests.md"><strong>Edit</strong> this page on GitHub</a></div>
diff --git a/docs/06-ModulesAndHelpers.md b/docs/06-ModulesAndHelpers.md
@@ -590,3 +590,7 @@ Helpers also can be used to extend the functionality of the original modules.
 
 * **Next Chapter: [ReusingTestCode >](/docs/06-ReusingTestCode)**
 * **Previous Chapter: [< UnitTests](/docs/05-UnitTests)**
+
+
+<p>&nbsp;</p>
+<div class="alert alert-warning"><a href="https://github.com/Codeception/codeception.github.com/edit/master/docs/06-ModulesAndHelpers.md"><strong>Edit</strong> this page on GitHub</a></div>
diff --git a/docs/07-AdvancedUsage.md b/docs/07-AdvancedUsage.md
@@ -836,3 +836,7 @@ and write them faster using the interactive console. Codeception tests can be ea
 
 * **Next Chapter: [BDD >](/docs/07-BDD)**
 * **Previous Chapter: [< ReusingTestCode](/docs/06-ReusingTestCode)**
+
+
+<p>&nbsp;</p>
+<div class="alert alert-warning"><a href="https://github.com/Codeception/codeception.github.com/edit/master/docs/07-AdvancedUsage.md"><strong>Edit</strong> this page on GitHub</a></div>
diff --git a/docs/08-Customization.md b/docs/08-Customization.md
@@ -498,3 +498,6 @@ If you see you have a problem that can be solved using these extensions, then gi
 
 * **Next Chapter: [Data >](/docs/09-Data)**
 * **Previous Chapter: [< BDD](/docs/07-BDD)**
+
+<p>&nbsp;</p>
+<div class="alert alert-warning"><a href="https://github.com/Codeception/codeception.github.com/edit/master/docs/08-Customization.md"><strong>Edit</strong> this page on GitHub</a></div>
diff --git a/docs/09-Data.md b/docs/09-Data.md
@@ -422,3 +422,6 @@ to operate with database through a data abstraction layer, and use the DataFacto
 
 * **Next Chapter: [APITesting >](/docs/10-APITesting)**
 * **Previous Chapter: [< Customization](/docs/08-Customization)**
+
+<p>&nbsp;</p>
+<div class="alert alert-warning"><a href="https://github.com/Codeception/codeception.github.com/edit/master/docs/09-Data.md"><strong>Edit</strong> this page on GitHub</a></div>
diff --git a/docs/10-APITesting.md b/docs/10-APITesting.md
@@ -386,8 +386,8 @@ class Api 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 has been created after the `CreateUser` call. You can improve testing scenarios by using REST or SOAP responses in your helper methods.
 
-
-
-
 * **Next Chapter: [Codecoverage >](/docs/11-Codecoverage)**
 * **Previous Chapter: [< Data](/docs/09-Data)**
+
+<p>&nbsp;</p>
+<div class="alert alert-warning"><a href="https://github.com/Codeception/codeception.github.com/edit/master/docs/10-APITesting.md"><strong>Edit</strong> this page on GitHub</a></div>
diff --git a/docs/11-Codecoverage.md b/docs/11-Codecoverage.md
@@ -216,8 +216,9 @@ Context stream options are [well documented at php.net](http://php.net/manual/en
 It's never been easier to setup local and remote code coverage. Just one config and one additional file to include!
 **With Codeception you can easily generate CodeCoverage reports for your Selenium tests** (or other acceptance or api tests). Mixing reports for `acceptance`, `functional`, and `unit` suites provides you with the most complete information on which parts of your applications are tested and which are not.
 
+* **Next Chapter: [ContinuousIntegration >](/docs/12-ContinuousIntegration)**
+* **Previous Chapter: [< APITesting](/docs/10-APITesting)**
 
 
-
-* **Next Chapter: [ContinuousIntegration >](/docs/12-ContinuousIntegration)**
-* **Previous Chapter: [< APITesting](/docs/10-APITesting)**
+<p>&nbsp;</p>
+<div class="alert alert-warning"><a href="https://github.com/Codeception/codeception.github.com/edit/master/docs/11-Codecoverage.md"><strong>Edit</strong> this page on GitHub</a></div>
diff --git a/docs/12-ContinuousIntegration.md b/docs/12-ContinuousIntegration.md
@@ -207,8 +207,8 @@ test:
 
 It is highly recommended to use Continuous Integration system in development. Codeception is easy to install and run in any CI systems. However, each of them has their differences you should take into account. You can use different reporters to provide output in format expected by CI system.
 
-
-
-
 * **Next Chapter: [ParallelExecution >](/docs/12-ParallelExecution)**
 * **Previous Chapter: [< Codecoverage](/docs/11-Codecoverage)**
+
+<p>&nbsp;</p>
+<div class="alert alert-warning"><a href="https://github.com/Codeception/codeception.github.com/edit/master/docs/12-ContinuousIntegration.md"><strong>Edit</strong> this page on GitHub</a></div>
diff --git a/docs/12-ParallelExecution.md b/docs/12-ParallelExecution.md
@@ -469,7 +469,7 @@ To create one command to rule them all we can define new public method `parallel
 
 Codeception does not provide tools for parallel test execution. This is a complex task and solutions may vary depending on a project. We use [Robo](http://robo.li) task runner as an external tool to perform all required steps. To prepare our tests to be executed in parallel we use Codeception features of dynamic groups and environments. To do even more we can create Extensions and Group classes to perform dynamic configuration depending on a test process.
 
-
-
-
 * **Previous Chapter: [< ContinuousIntegration](/docs/12-ContinuousIntegration)**
+
+<p>&nbsp;</p>
+<div class="alert alert-warning"><a href="https://github.com/Codeception/codeception.github.com/edit/master/docs/12-ParallelExecution.md"><strong>Edit</strong> this page on GitHub</a></div>
