Revert "run remark linter locally"

This reverts commit 97c348f1ae.

docs/ocis/testing.md

@@ -1,12 +1,12 @@
-* * *
-
+---
 title: "Testing"
 date: 2018-05-02T00:00:00+00:00
 weight: 37
-geekdocRepo: <https://github.com/owncloud/ocis>
+geekdocRepo: https://github.com/owncloud/ocis
 geekdocEditPath: edit/master/docs
+geekdocFilePath: testing.md
+---
 
-## geekdocFilePath: testing.md
 
 ## Acceptance tests
 
@@ -15,8 +15,9 @@ We are using the ownCloud 10 acceptance testsuite against ocis. To set this up y
 ### Getting the tests
 
 All you need to do to get the acceptance tests is check out the core repo:
-
-    git clone https://github.com/owncloud/core.git
+```
+git clone https://github.com/owncloud/core.git
+```
 
 ### Run a redis server in a docker container
 
@@ -27,24 +28,27 @@ File versions need a redis server. Start one with docker by using:
 ### Run ocis
 
 To start ocis:
-
-    bin/ocis server
+```
+bin/ocis server
+```
 
 ### Run the acceptance tests
-
 First we will need to clone the testing app in owncloud which contains the skeleton files required for running the tests.
 In the ownCloud 10 core clone the testing app with the following command:
 
-    git clone https://github.com/owncloud/testing apps/testing
+```
+git clone https://github.com/owncloud/testing apps/testing
+```
 
 Then run the api acceptance tests with the  following command:
-
-    make test-acceptance-api \
-    TEST_SERVER_URL=https://localhost:9200 \
-    TEST_OCIS=true \
-    OCIS_REVA_DATA_ROOT=/var/tmp/reva/ \
-    SKELETON_DIR=apps/testing/data/apiSkeleton \
-    BEHAT_FILTER_TAGS='~@notToImplementOnOCIS&&~@toImplementOnOCIS'
+```
+make test-acceptance-api \
+TEST_SERVER_URL=https://localhost:9200 \
+TEST_OCIS=true \
+OCIS_REVA_DATA_ROOT=/var/tmp/reva/ \
+SKELETON_DIR=apps/testing/data/apiSkeleton \
+BEHAT_FILTER_TAGS='~@notToImplementOnOCIS&&~@toImplementOnOCIS'
+```
 
 Make sure to adjust the settings `TEST_SERVER_URL` and `OCIS_REVA_DATA_ROOT` according to your environment.
 
@@ -80,30 +84,24 @@ If you want to work on a specific issue
 2.  locally run each of the tests marked with that issue in the expected failures file
 
     E.g.:
-
-        make test-acceptance-api \
-        TEST_SERVER_URL=https://localhost:9200 \
-        TEST_OCIS=true \
-        OCIS_REVA_DATA_ROOT=/var/tmp/reva/ \
-        BEHAT_FEATURE='tests/acceptance/features/apiComments/comments.feature:123'
+    ```
+    make test-acceptance-api \
+    TEST_SERVER_URL=https://localhost:9200 \
+    TEST_OCIS=true \
+    OCIS_REVA_DATA_ROOT=/var/tmp/reva/ \
+    BEHAT_FEATURE='tests/acceptance/features/apiComments/comments.feature:123'
+    ```
 
 3.  the tests will fail, try to understand how and why they are failing
-
 4.  fix the code
-
 5.  go back to 2. and repeat till the tests are passing.
-
 6.  remove those tests from the expected failures file
-
 7.  run each of the local tests that were demonstrating the **buggy** behavior. They should fail.
-
 8.  delete each of the local tests that were demonstrating the **buggy** behavior.
-
 9.  make a PR that has the fixed code, relevant lines removed from the expected failures file and bug demonstration tests deleted.
 
     If the changes also affect the `ocis-reva` repository make sure the changes get ported over there.
 
 ### Notes
-
--   in a normal case the test-code cleans up users after the test-run, but if a test-run is interrupted (e.g. by CTRL+C) users might have been left on the LDAP server. In that case rerunning the tests requires wiping the users in the ldap server, otherwise the tests will fail when trying to populate the users.
--   the tests usually create users in the OU `TestUsers` with usernames specified in the feature file. If not defined in the feature file, most users have the password `123456`, defined by `regularUserPassword` in `behat.yml`, but other passwords are also used, see [`\FeatureContext::getPasswordForUser()`](https://github.com/owncloud/core/blob/master/tests/acceptance/features/bootstrap/FeatureContext.php#L386) for mapping and [`\FeatureContext::__construct`](https://github.com/owncloud/core/blob/master/tests/acceptance/features/bootstrap/FeatureContext.php#L1668) for the password definitions.
+- in a normal case the test-code cleans up users after the test-run, but if a test-run is interrupted (e.g. by CTRL+C) users might have been left on the LDAP server. In that case rerunning the tests requires wiping the users in the ldap server, otherwise the tests will fail when trying to populate the users.
+- the tests usually create users in the OU `TestUsers` with usernames specified in the feature file. If not defined in the feature file, most users have the password `123456`, defined by `regularUserPassword` in `behat.yml`, but other passwords are also used, see [`\FeatureContext::getPasswordForUser()`](https://github.com/owncloud/core/blob/master/tests/acceptance/features/bootstrap/FeatureContext.php#L386) for mapping and [`\FeatureContext::__construct`](https://github.com/owncloud/core/blob/master/tests/acceptance/features/bootstrap/FeatureContext.php#L1668) for the password definitions.