Valinor
Infection
Valinor | Infection | |
---|---|---|
10 | 11 | |
1,236 | 1,983 | |
1.2% | 0.7% | |
8.8 | 8.5 | |
10 days ago | 22 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.
Valinor
-
PHP libraries and tools
cuyz/valinor: PHP library that helps to map any input into a strongly-typed value object structure.
- Data-Mapper: A package for fast mapping of strong-typed objects
- PHP RFC: Deprecations for PHP 8.3
- brick/json-mapper: map JSON data to strongly typed PHP DTOs
-
Hydration / Mapping library
I know there are alternatives like Valinor (https://github.com/CuyZ/Valinor)
-
[Bundle] Automatically map the incoming request data to a DTO and optionally validate it
For the next major version, i'm considering giving the option to use valinor (or anything else) instead of the Serializer component in the next major version. If you have more ideas, let me know.
-
Valinor — Object mapper with strong type support and error handling
You can check the repository on GitHub; there is also a documentation website.
-
pjson: a simple JSON <=> PHP8+ data objects library
See also: Valinor https://github.com/CuyZ/Valinor which does some of what you want, albeit in a more verbose fashion, but without polluting your objects.
- Valinor: a library that maps unstructured input to properly typed objects
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?
laravel-data - Powerful data objects for Laravel
Pest - Pest is an elegant PHP testing Framework with a focus on simplicity, meticulously designed to bring back the joy of testing in PHP.
Serde - Robust Serde (serialization/deserialization) library for PHP 8.
rector-laravel - Rector upgrades rules for Laravel
serializer - Handles serializing and deserializing data structures, including object graphs, into array structures or other formats like XML and JSON.
php-mysql-engine - A MySQL engine written in pure PHP
ObjectHydrator - Object Hydration library to create Command and Query objects.
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
data-transfer-object - Data transfer objects with batteries included
churn-php - Discover files in need of refactoring.