sebastian, to random
@sebastian@phpc.social avatar

If you install using Composer (which is not the recommended way) then you can now use both PHPUnit 9.6 and PHPUnit 10.5 in projects that depend on either PHP-Parser 4 or PHP-Parser 5.

https://github.com/sebastianbergmann/php-code-coverage/issues/1004

sebastian,
@sebastian@phpc.social avatar

The recommended way to use is to use the PHAR that we distribute:

https://docs.phpunit.de/en/10.5/installation.html#phar-or-composer

sebastian, to random
@sebastian@phpc.social avatar

This year (finally!) saw the release of PHPUnit 10:

https://phpunit.de/announcements/phpunit-10.html

sebastian,
@sebastian@phpc.social avatar

10 was most significant release in the history of the PHPUnit project.

This release is to PHPUnit what PHP 7 was to PHP: a massive cleanup, refactoring, and modernisation that lays the foundation for future development.

sebastian,
@sebastian@phpc.social avatar

Did you know that only less than 1% of users fund my work?

sebastian,
@sebastian@phpc.social avatar

According to GitHub, over 108,273 packages (and 2,642,614 repositories) depend on .

https://github.com/sebastianbergmann/phpunit/network/dependents

sebastian,
@sebastian@phpc.social avatar
sebastian,
@sebastian@phpc.social avatar

To everyone who does not already sponsor my work: please consider to do so! If you benefit from using PHPUnit, then it is in your best interest that I am able to continue to work on .

sebastian,
@sebastian@phpc.social avatar

You cannot buy , but you can pay for PHPUnit.

And the best way to do so benefits you, your team, and me: let me help you through consulting, coaching, and training:

https://thephp.cc/training/test-automation?ref=mastodon

sebastian,
@sebastian@phpc.social avatar

The easiest way to sponsor my work on is through GitHub Sponsors:

https://github.com/sponsors/sebastianbergmann

sebastian,
@sebastian@phpc.social avatar

You would like to see your company logo on 's website?

https://phpunit.de/sponsors.html

Contact me at sponsoring@phpunit.de to learn more about how you can support PHPUnit.

markusstaab, to opensource German
@markusstaab@phpc.social avatar

Put togehter a summary and my personal hightlights of 2023.

@phpstan @rectorphp @Mautic @symfony et. all

https://staabm.github.io/2023/12/07/contribution-summary-2023.html

sebastian, (edited ) to Symfony
@sebastian@phpc.social avatar

Here is the material that I used for my " 10 for Developers" at today:

https://thephp.cc/presentations/phpunit-10-for-symfony-developers?ref=mastodon

sebastian, to random
@sebastian@phpc.social avatar

Almost time for my presentation at .

pwaring, to php
@pwaring@fosstodon.org avatar

Adding some tests to a legacy PHP project. Much more challenging than with a brand new codebase, also building the infrastructure is harder when test frameworks assume you're using PSR-4 autoloading etc. I think the payoff is worth it though as it's helping to ensure that a patch to fix an edge case (roughly 1% of records) actually works without regressions.

sebastian, to random
@sebastian@phpc.social avatar

Do you think assertions that compare two arrays while ignoring a list of keys would be useful to have in ?

https://github.com/sebastianbergmann/phpunit/pull/5600

sebastian, to random
@sebastian@phpc.social avatar

Curious what's inside 's PHP Archive (PHAR)?

The special --manifest, --sbom, and --composer-lock CLI options can help you:

https://docs.phpunit.de/en/10.5/installation.html#what-is-inside-the-phar

sebastian, (edited ) to random
@sebastian@phpc.social avatar

Do you load (require, require_once, include, include_once, ...) the of ?

sebastian, to random
@sebastian@phpc.social avatar

Two months from now, on February 2, 2024, 11 will be release.

PHPUnit 11 is the annual major release for 2024 that removes deprecated functionality and lays the foundation for delivering features and improvements throughout the year in PHPUnit 11.1 (April), PHPUnit 11.2 (June), PHPUnit 11.3 (August), PHPUnit 11.4 (October), and PHPUnit 11.5 (December).

phpunit, to random
@phpunit@phpc.social avatar
mattsches, to random German
@mattsches@phpc.social avatar
sebastian, to Symfony German
@sebastian@phpc.social avatar

Am Donnerstag, den 14. Dezember 2023 werde ich die in Köln [be|heim]suchen, um einen Vortrag über 10 zu halten.

phpunit, to random
@phpunit@phpc.social avatar
sebastian, to php German
@sebastian@phpc.social avatar

In ungefähr einer Stunde mache ich mich auf den Weg nach .

Dort halte ich morgen auf der @ContaoCommunity einen Vortrag darüber, was sich in letzter Zeit bei und so getan hat.

Nach dem Vortrag werde ich mein Material auf https://thephp.cc/praesentationen?ref=mastodon veröffentlichen.

brotkrueml, to php
@brotkrueml@phpc.social avatar

Tip: Do not use testdox="true" on 10 with functional tests: bootstrap errors, like DI failures, are then not displayed in detail anymore (just the "E").

Figured it out for you in the last hours.

Flyingmana, to php
@Flyingmana@phpc.social avatar

ugh, trying for days now to find out why my phpunit tests do not provide coverage for
Slowly getting the feeling I managed to create a special case of phpunit config, which makes matching the code for the coverage not working in special circumstances.

but running it local with identic versions does work 🙄

Flyingmana,
@Flyingmana@phpc.social avatar
  • All
  • Subscribed
  • Moderated
  • Favorites
  • megavids
  • thenastyranch
  • rosin
  • GTA5RPClips
  • osvaldo12
  • love
  • Youngstown
  • slotface
  • khanakhh
  • everett
  • kavyap
  • mdbf
  • DreamBathrooms
  • ngwrru68w68
  • provamag3
  • magazineikmin
  • InstantRegret
  • normalnudes
  • tacticalgear
  • cubers
  • ethstaker
  • modclub
  • cisconetworking
  • Durango
  • anitta
  • Leos
  • tester
  • JUstTest
  • All magazines