Infection 0.33.0 has been released.
- Testo test framework support (by @roxblnfk)
- Allow using the full width of the terminal for console output
Enjoy!
| Docs | https://infection.github.io/guide/ |
| GitHub | https://github.com/infection/infection |
| Playground | https://infection-php.dev/ |
Infection 0.33.0 has been released.
- Testo test framework support (by @roxblnfk)
- Allow using the full width of the terminal for console output
Enjoy!
@blackwolf12333 Cool, let us please know how it goes.
We are interested in how developers use it with AI nowadays so we better understand where to pay our attention to.
Do you use Infection with AI-generated code/tests? If so, what is the workflow / skills / prompts?
Is there anything we need to improve here to make it more useful?
Now officially: Infection supports killing mutants by Static Analysis tools:
- PHPStan
- Mago
https://infection.github.io/guide/static-analysis-integration.html
Enjoy!
Question to get an idea and inspiration: what do you run in CI?
I run:
- composer install + validate + audit
- php lint
- deptrac
- ecs
- @phpmd
- @phpunit (with and without database)
- @infection_php
- @phpstan
- Vi test
- rector
- mlc
- vale
- redoc-cli
- Custom script to build documentation from a combination of markdown, openapi and test results.
- a manual job to create a new release (combine all changelogs from a directory to a main changelog, create a tag, push)
Infection 0.32.3 has been released with new `--max-timeouts` and `--with-timeouts` options.
Read the details in this blog post to understand how it helps with speeding up Mutation Testing and why you should start using them!
๐ Xmas present
Infection 0.32.0 has been released:
- Format-presering pretty printing
- new GitHub loggers with collapsable sections
- Symfony 8 support; webmozart/assert@v2 support
- and much more
Added: Support --exclude-source-from-xml-coverage fast path for PHPUnit 12.5+ by @staabm in #2604 Implement GitHubActionsLogTextFileLogger to improve DX of text file logger with GA by @staabm in #...
Looks like @phpunit xml-report code-coverage generation could get nearly twice as fast in the future.
this would for example considerably reduce overhead of the necessary "initial-test" step when running @infection_php on your project.