Page MenuHomeDevCentral

Configure PHPUnit and PHP_CodeSniffer
ClosedPublic

Authored by dereckson on Feb 21 2022, 03:02.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Nov 16, 01:36
Unknown Object (File)
Thu, Nov 14, 22:05
Unknown Object (File)
Mon, Nov 11, 20:21
Unknown Object (File)
Mon, Nov 11, 06:21
Unknown Object (File)
Sun, Nov 10, 06:20
Unknown Object (File)
Sat, Nov 9, 13:07
Unknown Object (File)
Sat, Nov 9, 12:14
Unknown Object (File)
Sat, Nov 9, 12:03
Subscribers
None

Details

Summary

Quality tools like phpunit and phpcs can run across all the repository
testing and linting all libraries at once.

Some configuration files will be dynamic and grow when we add more
libraries to the repository.

As such, maintain a small collection of metadata on the libraries
allows to create templates.

Templates use Jinja2 and are rendered by a small Python script.

Each time a library is added to the repository, make regenerate
allows to create those files. Autogenerated files are stable enough
to be included in the repository too.

Ref T1680

Test Plan

make regenerate, then phpunit and phpcs

Diff Detail

Repository
rKERUALD Keruald libraries development repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable