Skip to content

Latest commit

 

History

History
79 lines (54 loc) · 2.81 KB

testing.md

File metadata and controls

79 lines (54 loc) · 2.81 KB
Raw

Testing

Different parts of the code can be tested in isolation. This allows for a test suite that runs very fast, and can therefore be run very often, keeping the feedback loop as short as possible. The test suite can also be executed locally as well as on a continuous integration server, which also helps the developer to get feedback as quickly as possible.

You can run all test combined with:

composer test

Continuous integration

Using Travis CI, the full test suite will be run against every pull request and has to pass before it can be merged. Every commit on the master branch will be tested as well.

Static analysis

Before the tests are run, a number of tools will be used to analyse the source code and detect issues that should be fixed:

  • A PHP linter checks the PHP code for syntax errors that will prevent the code from being interpreted. This includes test code as well as production code;
  • The Twig templates and YAML files are checked for syntax errors as well;
  • The composer.json and composer.lock files are being validated;
  • PHP Mess Detector checks a number of metrics, and if they exceed a certain treshold the build will fail;
  • PHP CodeSniffer ensures that the code adheres to the chosen coding standard (PSR-2);
  • PHP Copy-Paste Detector ensures that there is no substantial duplication within the source code.

You can run these tools manually with composer:

composer lint

composer static-analysis

Unit testing

Unit testing verifies that the individual units of source code are working properly, by isolating them from the rest of the application. A unit is the smallest testable part of code, typically a class. The purpose of unit testing is to provide design feedback during the development phase, to ensure that code conforms to specifications and to ensure that future modifications do not introduce unintended side effects.

You can run these tools manually with composer:

composer phpunit

Acceptance testing

Acceptance tests test the actual features that the software delivers. It does so by running the application code (command handlers) in combination with the domain code. The infrastructure (databases, external systems) are replaced with stand-ins in order to make the test suite faster.

Acceptance tests will be written for all command handlers and will be run as part of every CI build.

You can run these tools manually with composer:

composer behat

Security testing

Using an automated tool, the list of dependencies of the project is being checked against a database of known vulnerabilities as part of every CI build. If any of the dependencies contains a known vulnerability, the build will fail.

Tools: SensioLabs Security Checker Yarn audit

You can run these tools manually with composer:

composer security-tests