update tests documentation (#162)

* Update sourcecode testing section

* Update linting section

* nfo about launching tests "as in ci" + note about phpunit

* Update source/sourcecode.rst

Co-authored-by: Johan Cwiklinski <trasher@x-tnd.be>

---------

Co-authored-by: Sebastien Monterisi <smonterisi@teclib.com>
Co-authored-by: Johan Cwiklinski <trasher@x-tnd.be>

Author: SebSept

source/codingstandards.rst

@@ -245,33 +245,9 @@ Examples:
 Checking standards
 ------------------
 
-In order to check standards are respected, we provide a defaut configuration for `PHP CodeSniffer <http://pear.php.net/package/PHP_CodeSniffer>`_ rules. From the GLPI directory, just run:
+Linting (checking and fixing coding standards) is a good way to ensure code quality and consistency of the code base.
+This is done using [PHP CodeSniffer](https://github.com/squizlabs/PHP_CodeSniffer), [PHPStan](https://phpstan.org/), [ESLint](https://eslint.org/), [Stylelint](https://stylelint.io/) and [TwigCS](https://github.com/friendsoftwig/twigcs).
 
-.. code-block::
-
-   phpcs .
-
-If the above command does not provide any output, then, all is OK :)
-
-An example error output would looks like:
-
-.. code-block:: bash
-
-   phpcs .
-   
-   FILE: /var/www/webapps/glpi/tests/HtmlTest.php
-   ----------------------------------------------------------------------
-   FOUND 3 ERRORS AFFECTING 3 LINES
-   ----------------------------------------------------------------------
-    40 | ERROR | [x] Line indented incorrectly; expected 4 spaces, found
-       |       |     3
-    59 | ERROR | [x] Line indented incorrectly; expected 4 spaces, found
-       |       |     3
-    64 | ERROR | [x] Line indented incorrectly; expected 4 spaces, found
-       |       |     3
-
-To automatically fix most of the issues, use `phpcbf`, it will per default rely on default configuration:
-
-.. code-block::
-
-   phpcbf .
+This can run the tasks using Docker, on your local host use `./tests/run_tests.sh lint` to proceed to all linting tasks, or use a scoped task, `./tests/run_tests.sh lint_php` to proceed to PHP linting only for example.
+All possible lintings are listed in the `./tests/run_tests.sh` script.
+For faster action you can run the scripts on your local machine or Docker development container using `node_modules/.bin/eslint . && echo "ESLint found no errors"` for example. You can find all the commands in [`.github/actions` directory](https://github.com/glpi-project/glpi/tree/main/.github/actions).

source/sourcecode.rst

@@ -37,7 +37,9 @@ Those branches are created when a new major or intermediate version is released.
 Testing
 -------
 
-There are more and more unit tests in GLPI; we use the `atoum unit tests framework <http://atoum.org>`_.
+Testing is a very important part of the development process.
+The reference for tests is the `GitHub CI <https://github.com/glpi-project/glpi/blob/main/.github/workflows/ci.yml>`_.
+The easier way to proceed with testing is to use the provided test script `run_tests.sh <https://github.com/glpi-project/glpi/blob/main/tests/run_tests.sh>`_ which uses Docker and bootstrap everything needed.
 
 Every proposal **must** contains unit tests; for new features as well as bugfixes. For the bugfixes; this is not a strict requirement if this is part of code that is not tested at all yet. See the :ref:`unit testing section <unittests>` at the bottom of the page.
 
@@ -260,7 +262,7 @@ Unit testing (and functional testing)
 
    A note for the purists... In GLPI, there are both unit and functional tests; without real distinction ;-)
 
-We use the `atoum unit tests framework <http://atoum.org>`_ for PHP tests; see `GLPI website if you wonder why <http://glpi-project.org/spip.php?breve375>`_.
+We use `PHPUnit <https://phpunit.de>`_ for tests.
 `atoum`'s documentation in available at: http://docs.atoum.org
 
 For JavaScript tests, GLPI uses the Jest testing framework.