Re:Catching bugs early with static analysis
by phpdave11 on Monday August 12, 2019 @09:12AM
(#20675058)
PHPStan is a great tool. In addition to PHPStan, I also use phpnsc (name space checker) to check for missing use statements, php-cs-fixer (code style fixer) to ensure the code adheres to my code style, phpcpd (copy paste detector) to detect duplicate code, and phpmd (mess detector) to find potential problems in the code. These are all set up in my CI pipeline so that my app will fail to build if any of these 5 tools detect a problem. It has saved me from deploying buggy code several times.
[ Parent
| on HN ]
Re:Catching bugs early with static analysis
by blowski on Monday August 12, 2019 @01:29PM
(#20677709)
Here’s a GitHub repo and Docker image with lots more static analysis tools to play with:
Re:Catching bugs early with static analysis
by king7532 on Monday August 12, 2019 @10:17AM
(#20675594)
Great advice and thank you for sharing! Do you have a Dockerfile or CI config/recipe that you could share?
Re:Catching bugs early with static analysis
by phpdave11 on Monday August 12, 2019 @10:33AM
(#20675741)
Here's the bash script I use to do the code validation. It's called from within my Dockerfile.
https://gist.github.com/phpdave11/412893f8366cab0afa85e81a7a...
Re:Catching bugs early with static analysis
by andreascreten on Monday August 12, 2019 @09:13AM
(#20675064)
Makes sense, thanks for sharing!