Fixed static tests

Author: sivaschenko

src/contributor-guide/pull-request-tests.md

@@ -21,27 +21,34 @@ Semantic Version Checker is a test that compares the changed code against the ma
 Please see the [Backward Compatibility Development Guide](https://devdocs.magento.com/guides/v2.3/contributor-guide/backward-compatible-development/index.html) for more information
 
 ### Functional Tests
+
 Functional Tests are PHPUnit-based tests that check Magento functional behavior from the perspective of a user. They press buttons and links in browser, fill and submit forms, look and check what is displayed in the browser's window like real users.
 
 ### Sample Data Tests
+
 Sample Data Tests are functional tests that run on Magento with Sample Data included.
 
 ### Unit Tests
+
 Unit tests are PHPUnit-based (for PHP) and Jasmine-based (for JS) tests which check the behavior of single methods of Magento classes. The purpose is to validate that each unit of Magento performs as designed.
 
 ### Integration Tests
+
 Integration Tests are PHPUnit-based tests that check the behaviour of group of Magento components. They include three types of tests:
-* Standard Integration tests which check Magento behavior on installed instance.
-* Setup Integration tests which check Magento behavior during the installation process.
-* Integration Integrity tests which check the consistency of installed Magento instance (configuration files, DB schemes etc.)
+
+-  Standard Integration tests which check Magento behavior on installed instance.
+-  Setup Integration tests which check Magento behavior during the installation process.
+-  Integration Integrity tests which check the consistency of installed Magento instance (configuration files, DB schemes etc.)
 
 ### WebAPI Tests
 WebAPI Tests are functional tests that check the behavior of Magento Web API endpoints. They send requests to endpoints of installed Magento instance and and then check the response received and the state of the instance. Currently they include three kinds of tests:
+
 -  SOAP Web API tests
 -  REST Web API tests
 -  GraphQL WEB API tests
 
 ### Static Tests
+
 Static Tests are set of different checks that analyze each single file of Magento code base separately. Most of them analyze the whole Magento code base whereas some run only against the change set.
 
 ### Database Compare
@@ -51,49 +58,21 @@ Database Compare is a test which compares DB schema and data between freshly ins
 ### Magento Component Health Index
 
 Magento Component Health Index is a test which analyses Magento code quality and calculates weighted health index (100 is great, lower is worse) per Magento Component (module). The index is calculated based on 3 groups of indicators:
--  General code quality indicators (GCQI). The metrics described [here](http://pdepend.org/documentation/software-metrics/index.html):
-  -  Inheritance rate
-  -  Coupling Between Objects
-  -  Cyclomatic Complexity Number
-  -  Class Size
-  -  NPath Complexity
-  -  Code Rank
-  -  Number Of Methods
-  -  Number Of Child Classes
--  Magento-specific code quality indicators (MSCQ):
-  -  Inline JS usage (<script> tag without attribute **x-magento-init** or **x-magento-template**)
-  -  PHP Static method calls (except unit tests)
-  -  PHP global state usage (global variables usage & static local variable usage, registry object usage)
-  -  PHP usage of protected modifiers for methods & properties (except unit tests)
-  -  PHP and JS 'fixmeComments' usage (**TODO**, **FIXME**, **HACK**, **XXX**, **@SuppressWarnings** etc.)
--  Legacy API usage indicators (LAI):
-   -  Legacy method calls in action classes (**loadLayout()**, **renderLayout()** etc.)
-   -  Legacy classes extension (**\Magento\Backend\Block\Widget\Grid\Extended**, **\Magento\Backend\Block\Widget\Form**, **\Magento\Backend\Block\Widget\Form\Generic**, **\Magento\Payment\Model\Method\AbstractMethod**, **\Magento\Payment\Model\Method\Cc**, **\Magento\Backend\Block\Widget\Grid** etc.)
-   -  Legacy layout block classes usage
-   -  Direct class calls instead of an interface that has DI preference
-   -  Comparison of composer dependencies against etalon file
+
+-  General code quality indicators (GCQI). The metrics described [here](http://pdepend.org/documentation/software-metrics/index.html)
+-  Magento-specific code quality indicators (MSCQ)
+-  Legacy API usage indicators (LAI)
 
 ## Running tests for a pull request {#run-pull-request-tests}
 
 Automated tests can be triggered manually with an appropriate comment:
+
 -  `@magento run all tests` - run or re-run all required tests against the PR changes
 -  `@magento run <test-build(s)>` - run or re-run specific test build(s)
-  For example: `@magento run Unit Tests` or `@magento run Unit Tests,Integration Tests`
-
-`<test-build(s)>` is a comma-separated list of build names. Allowed build names are:
-
-1. `Database Compare`
-2. `Functional Tests CE`
-3. `Functional Tests EE`,
-4. `Functional Tests B2B`
-5. `Integration Tests`
-6. `Magento Health Index`
-7. `Sample Data Tests CE`
-8. `Sample Data Tests EE`
-9. `Sample Data Tests B2B`
-10. `Static Tests`
-11. `Unit Tests`
-12. `WebAPI Tests`
+
+For example: `@magento run Unit Tests` or `@magento run Unit Tests,Integration Tests`
+
+`<test-build(s)>` is a comma-separated list of build names. Build names can be copied from the Checks section.
 
 ## Test results
 
@@ -107,7 +86,7 @@ When the contribution requires changes to more than one repository merged simult
 
 The related pull requests should be specified in the pull request description in the following format:
 
-```
+```lang-none
 ### Related Pull Requests
 https://github.com/<organization>/<repository>/pull/<pull request number>
 <links to other realted PRs>