auto updated documentation

DavertMik · DavertMik · commit 18b7344f9269 · 2017-01-17T22:50:12.000+02:00
diff --git a/docs/12-ContinuousIntegration.md b/docs/12-ContinuousIntegration.md
@@ -88,7 +88,7 @@ Jenkins should locate `report.html` at `tests/_output/`. Now Jenkins will displa
 
 ## TeamCity
 
-![TeamCity](http://codeception.com/images/teamcity.png)
+![TeamCity](http://codeception.com/images/teamcity/logo.jpg)
 
 TeamCity is a hotsed solution from JetBrains. The setup of it can be a bit tricky as TeamCity uses its own reporter format for parsing test results. PHPUnit since verison 5.x has integrated support for this format, so does Codeception. What we need to do is to configure Codeception to use custom reporter. By default there is `--report` option which provides an alternative output. You can change the reporter class in `codeception.yml` configuration:
 
@@ -112,7 +112,7 @@ After you create build project you should define build step with Codeception whi
 
 Once you execute your first build you should see detailed report inside TeamCity interface:
 
-![report](http://codeception.com/images/teamcity/report.png)
+![report](http://codeception.com/images/teamcity/report2.png)
 
 ## TravisCI
 
@@ -132,9 +132,9 @@ Travis doesn't provide visualization for XML or HTML reports so you can't view r
 
 ## GitLab
 
-If a file {% highlight yaml %}
-.gitlab-ci.yml
-{% endhighlight %} exists in the root of the git repository, gitlab will run a pipeline each time you push to the gitlab server. The file configures the docker image that will be called. Below is a sample which loads a php7 docker image, clones your files, installs composer dependencies, runs the built-in php webserver and finally runs codeception:
+![report](http://codeception.com/images/gitlab/logo.png)
+
+If a file `.gitlab-ci.yml` exists in the root of the git repository, GitLab will run a pipeline each time you push to the gitlab server. The file configures the docker image that will be called. Below is a sample which loads a php7 docker image, clones your files, installs composer dependencies, runs the built-in php webserver and finally runs codeception:
 
 {% highlight yaml %}
 
@@ -163,6 +163,10 @@ test:
 
 {% endhighlight %}
 
+![report](http://codeception.com/images/gitlab/build.png)
+
+For acceptance testing you can use `codeception/codeception` docker image as base.
+
 ## Conclusion
 
 It is tringly 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 repoters to provide output in format expected by CI system.
