#phpstan — Public Fediverse posts

"No single technique is sufficient. Static analysis detects obvious errors at low cost. Traditional dynamic testing with PHPUnit verifies specific behaviours. Property-based testing generalises these behaviours. Mutation testing validates the quality of the test suite. Fuzz testing explores the unknown."
https://phpunit.expert/articles/everything-we-have.html

#php #phpunit #psalm #phpstan etc.

"No single technique is sufficient. Static analysis detects obvious errors at low cost. Traditional dynamic testing with PHPUnit verifies specific behaviours. Property-based testing generalises these behaviours. Mutation testing validates the quality of the test suite. Fuzz testing explores the unknown."
https://phpunit.expert/articles/everything-we-have.html

#php #phpunit #psalm #phpstan etc.

"No single technique is sufficient. Static analysis detects obvious errors at low cost. Traditional dynamic testing with PHPUnit verifies specific behaviours. Property-based testing generalises these behaviours. Mutation testing validates the quality of the test suite. Fuzz testing explores the unknown."
https://phpunit.expert/articles/everything-we-have.html

#php #phpunit #psalm #phpstan etc.

"No single technique is sufficient. Static analysis detects obvious errors at low cost. Traditional dynamic testing with PHPUnit verifies specific behaviours. Property-based testing generalises these behaviours. Mutation testing validates the quality of the test suite. Fuzz testing explores the unknown."
https://phpunit.expert/articles/everything-we-have.html

#php #phpunit #psalm #phpstan etc.

"No single technique is sufficient. Static analysis detects obvious errors at low cost. Traditional dynamic testing with PHPUnit verifies specific behaviours. Property-based testing generalises these behaviours. Mutation testing validates the quality of the test suite. Fuzz testing explores the unknown."
https://phpunit.expert/articles/everything-we-have.html

#php #phpunit #psalm #phpstan etc.

Hey #php developers out there 👀 👋

What tools do you use to make your #ai write "good" code? 😏

#phpstan, #psalm, #mago, cs-fixer, #coderabbit...? 🤔
What's your most important tool? 🤔 #coding

Статанализ — must-have для проектов с Codex/ClaudeCode

На днях у Кирилла Мокевнина вышел пост про то, как он разлюбил динамическую типизацию. Мысль понятная: на больших кодовых базах отсутствие типов начинает дорого стоить. Хочу дополнить аргументом, который в 2026 году уже стал прям must-have: статанализ и типы — это лучший self-check для AI-агента . Современные агенты для разработки (Claude Code на Opus 4.5 и ChatGPT Codex 5.2 High) хорошо пишут код. Ошибок уровня «переменная не объявлена», «импорт забыл», «опечатка в имени метода» по сути уже почти нет. Основные промахи чаще про другое:

https://habr.com/ru/articles/993004/

#статистический_анализ #статический_анализ_кода #ruff #phpstan #phpcsfixer #php #python #go #codex #claude_code

The other night I made this little #PHP tool that validates #PHPDoc annotations against the actual method signature, to make sure that they are compatible and don't drift apart over time.

I use it as a quick check before running #PHPStan to make sure that the static analysis is correctly informed. Published it on #Packagist in case anyone else would find it useful too: https://packagist.org/packages/nsrosenqvist/phpdoc-validator

The other night I made this little #PHP tool that validates #PHPDoc annotations against the actual method signature, to make sure that they are compatible and don't drift apart over time.

I use it as a quick check before running #PHPStan to make sure that the static analysis is correctly informed. Published it on #Packagist in case anyone else would find it useful too: https://packagist.org/packages/nsrosenqvist/phpdoc-validator

The other night I made this little #PHP tool that validates #PHPDoc annotations against the actual method signature, to make sure that they are compatible and don't drift apart over time.

I use it as a quick check before running #PHPStan to make sure that the static analysis is correctly informed. Published it on #Packagist in case anyone else would find it useful too: https://packagist.org/packages/nsrosenqvist/phpdoc-validator

The other night I made this little #PHP tool that validates #PHPDoc annotations against the actual method signature, to make sure that they are compatible and don't drift apart over time.

I use it as a quick check before running #PHPStan to make sure that the static analysis is correctly informed. Published it on #Packagist in case anyone else would find it useful too: https://packagist.org/packages/nsrosenqvist/phpdoc-validator

The other night I made this little #PHP tool that validates #PHPDoc annotations against the actual method signature, to make sure that they are compatible and don't drift apart over time.

I use it as a quick check before running #PHPStan to make sure that the static analysis is correctly informed. Published it on #Packagist in case anyone else would find it useful too: https://packagist.org/packages/nsrosenqvist/phpdoc-validator

I kind of envy the java world. They have the alternatives on the IDE landscape and also the static analysis that are built-in are way better. In #php we still get #phpstan #psalm that do excelent job, but there are some corner scenarios that "the other kids toys" are better.

Updating (#PHP) packages to @reactphp Promise v3, and test your types with @phpstan: https://blog.wyrihaximus.net/2024/06/updating-php-packages-to-reactphp-promise-v3--and-test-your-types-with-phpstan/

#php #reactphp #phpstan #staticanalysis #template #strongtyping