phpstan-disallowed-calls
PHPStan rules to detect disallowed method & function calls, constant, namespace, attribute & superglobal usages (by spaze)
Infection
PHP Mutation Testing library (by infection)
| phpstan-disallowed-calls | Infection | |
|---|---|---|
| 3 | 11 | |
| 211 | 1,983 | |
| - | 0.7% | |
| 7.9 | 8.5 | |
| 13 days ago | 22 days ago | |
| PHP | PHP | |
| MIT License | BSD 3-clause "New" or "Revised" License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
phpstan-disallowed-calls
Posts with mentions or reviews of phpstan-disallowed-calls.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-11-09.
- Microservices aren't the problem. Incompetent people are
-
Weekly "ask anything" thread
Maybe I found it myself: https://github.com/spaze/phpstan-disallowed-calls
-
PHP libraries and tools
spaze/phpstan-disallowed-calls: PHPStan rules to detect disallowed calls and constant & namespace usages
Infection
Posts with mentions or reviews of Infection.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-10-18.
-
PHP: testing, "Attention please!"
consider adding mutation tests
-
Who tests the tests? Mutation testing with Infection in PHP
Obviously, we can not generate mutants manually. For that purpose, there are mutation testing utilities. For PHP, we have Infection.
-
PHP libraries and tools
Infection: PHP Mutation Testing library. Plugins: roave/infection-static-analysis-plugin: Static analysis on top of mutation testing - prevents escaped mutants from being invalid according to static analysis bitexpert/captainhook-infection: Captain Hook Plugin to run InfectionPHP only against the changed files of a commit
Infection: PHP Mutation Testing library. Plugins: roave/infection-static-analysis-plugin: Static analysis on top of mutation testing - prevents escaped mutants from being invalid according to static analysis bitexpert/captainhook-infection: Captain Hook Plugin to run InfectionPHP only against the changed files of a commit
-
I created a package to encourage developers in my team to write tests. What do you think? Any feedback? Thanks!
If you want to enforce testing automatically probably the best option is to rely on mutation testing, using Infection. That doesn't just check that the tests cover the code, it checks that if the code was different to what it is then the tests would (usually) fail.
-
Collecting line, branch, and path coverage with PHPUnit
IMO code coverage is a very flawed metric on its own. A high percentage doesn't guarantee that the tests actually test the right things, and it would be much more efficient if mutation testing was used (e.g. Infection). It still uses the generated code coverage reports, but only as a base for its own metrics.
-
Am I writing the right kinds of (unit) tests? See below for an example. Thanks!
For your last edit - you can also add infection which will infect your code with other values, like if you expect a positive number, it will try and inject a negative number - and see what happens - does your code break everything or something. Also it will try to inject false where you might expect a true and many many other things, and yes you will get some weird results from infection, but its a good thing to look at, and atleast check the logs and see why the infection failed at a test.
- I'm looking for "complex" or "advanced" topics that don't get enough coverage
-
Codewars Kata. It uses 100 random tests for a boolean.
The only one that I've used is infection for PHP.
-
Verify your true code coverage by removing lines of PHP code, see if it affects PHPUnit results
That's practically a light form of mutant testing. Have you checked Infection?
What are some alternatives?
When comparing phpstan-disallowed-calls and Infection you can also consider the following projects:
phpinsights - 🔰 Instant PHP quality checks from your console
Pest - Pest is an elegant PHP testing Framework with a focus on simplicity, meticulously designed to bring back the joy of testing in PHP.
Serializer - Library for (de-)serializing data of any complexity (supports JSON, and XML)
rector-laravel - Rector upgrades rules for Laravel
Deptrac - Keep your architecture clean.
php-mysql-engine - A MySQL engine written in pure PHP
nocolor - Validate the architecture of your PHP project based on the concept of function colors
ParaTest - :computer: Parallel testing for PHPUnit
Psalm - A static analysis tool for finding errors in PHP applications
psalm-plugin-phpunit - A PHPUnit plugin for Psalm
Robo - Modern task runner for PHP
churn-php - Discover files in need of refactoring.
phpstan-disallowed-calls vs phpinsights
Infection vs Pest
phpstan-disallowed-calls vs Serializer
Infection vs rector-laravel
phpstan-disallowed-calls vs Deptrac
Infection vs php-mysql-engine
phpstan-disallowed-calls vs nocolor
Infection vs ParaTest
phpstan-disallowed-calls vs Psalm
Infection vs psalm-plugin-phpunit
phpstan-disallowed-calls vs Robo
Infection vs churn-php