BackwardCompatibilityCheck
Infection
BackwardCompatibilityCheck | Infection | |
---|---|---|
3 | 11 | |
562 | 1,987 | |
0.9% | 0.9% | |
8.3 | 8.5 | |
13 days ago | 7 days ago | |
PHP | PHP | |
MIT License | BSD 3-clause "New" or "Revised" License |
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.
BackwardCompatibilityCheck
-
Some thoughts on the Interface Default Methods RFC
It's also not a big risk because if it does fail it will fail every time you just load the class that implements the interface so probably your while site will error. If you do cursory testing of the new version before you deploy it you can find the problem quickly before it becomes a problem. You can also do static analysis checks on your code to make sure its compatible with the libraries you use including when you upgrade them. And library maintainers can run Roave/BackwardCompatibilityCheck/ to make sure they don't accidentally introduce a new interface method without declaring a new major version.
-
PHP libraries and tools
roave/backward-compatibility-check: Tool to compare two revisions of a class API to check for BC breaks
-
PHP 8.1 is getting Enums, and here is an article about Enums in depth
btw when I talk about breaking BC I don't really mean not compatible with something stored in the DB using a previous version of the code. I mean not compatible with other PHP code written to work with a previous version of the code. It's the sort of issue https://github.com/Roave/BackwardCompatibilityCheck exists to detect, and for which semver says you have to increase the major version number on a library.
Infection
-
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?
Spout - Read and write spreadsheet files (CSV, XLSX and ODS), in a fast and scalable way
Pest - Pest is an elegant PHP testing Framework with a focus on simplicity, meticulously designed to bring back the joy of testing in PHP.
psalm-plugin-phpunit - A PHPUnit plugin for Psalm
rector-laravel - Rector upgrades rules for Laravel
psalm-plugin-doctrine - Stubs to let Psalm understand Doctrine better
php-mysql-engine - A MySQL engine written in pure PHP
local-php-security-checker - PHP security vulnerabilities checker
ParaTest - :computer: Parallel testing for PHPUnit
SecurityAdvisories - :closed_lock_with_key: Security advisories as a simple composer exclusion list, updated daily
no-leaks - :potable_water: PHPUnit Plugin for detecting Memory Leaks in code and tests
churn-php - Discover files in need of refactoring.