ISO-codes
Infection
Our great sponsors
ISO-codes | Infection | |
---|---|---|
1 | 10 | |
787 | 1,970 | |
- | 0.9% | |
2.9 | 8.3 | |
about 1 month ago | 3 days ago | |
PHP | PHP | |
GNU General Public License v3.0 only | 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.
ISO-codes
-
PHP libraries and tools
ronanguilloux/isocodes: PHP library - Validators for standards from ISO, International Finance, Public Administrations, GS1, Manufacturing Industry, Phone numbers & Zipcodes for many countries
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.
-
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.
-
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?
Respect Validation - The most awesome validation engine ever created for PHP
Pest - Pest is an elegant PHP testing Framework with a focus on simplicity, meticulously designed to bring back the joy of testing in PHP.
DMS Filter - Library that offers Input Filtering based on Annotations for use with Objects. Check out 2.dev for 2.0 pre-release.
MetaYaml - A powerful schema validator!
Linio Input - Abstracts HTTP request input handling, providing an easy interface for data hydration and validation
Valitron - Valitron is a simple, elegant, stand-alone validation library with NO dependencies
PHP validate - Lightweight and feature-rich PHP validation and filtering library. Support scene grouping, pre-filtering, array checking, custom validators, custom messages. 轻量且功能丰富的PHP验证、过滤库。支持场景分组,前置过滤,数组检查,自定义验证器,自定义消息。
Cake Validation - [READ-ONLY] Validation library from CakePHP. This repo is a split of the main code that can be found in https://github.com/cakephp/cakephp
Upload - File uploads with validation and storage strategies
Aura.Filter - Validate and sanitize arrays and objects.
rector-laravel - Rector upgrades rules for Laravel
php-mysql-engine - A MySQL engine written in pure PHP