Here is the material I used for my "So you think you know #PHPUnit?" at #IntPHPCon today:

https://thephp.cc/presentations/so-you-think-you-know-phpunit?ref=mastodon

Dear #PHP / #PHPUnit Community,

I am aware that https://phpunit.de/ and https://phar.phpunit.de/ (as well other domains of mine) are currently unreachable due to expired SSL certificates.

Service will be restored as soon as possible, but it's the weekend, so it may take until Monday.

Sorry!

OK PHP folks I am trying to add PHPUnit specific assertion to use with leage/csv

see https://github.com/thephpleague/csv/issues/562 for more information #csv #assertions #phpunit

#PHPUnit 12.1.6 has been released: https://github.com/sebastianbergmann/phpunit/releases/tag/12.1.6

#PHPUnit 11.5.21 has been released: https://github.com/sebastianbergmann/phpunit/releases/tag/11.5.21

@zapiz Xdebug is amazing, as others have suggested.

I also ensure full coverage with unit tests, using PHPUnit.

#PHP #Xdebug #PHPUnit

#PHPUnit 12.1.5 has been released: https://github.com/sebastianbergmann/phpunit/releases/tag/12.1.5

#PHPUnit 11.5.20 has been released: https://github.com/sebastianbergmann/phpunit/releases/tag/11.5.20

Anyone who uses Paratest: do you have to do anything special to get it to run your test bootstrap per process? I have vlucas/phpdotenv loading env vars in my bootstrap, but when running with Paratest, none of the env vars are present.

I’ve tried using --bootstrap, and that doesn’t help.

I’m using $_ENV to access the env vars, in case that matters.

#PHP #PHPUnit #Paratest

In @phpunit, is it possible to write custom attributes for test methods that trigger some hook before/after a test? Like, I want to say "before this test runs, pass this attribute's values to this hook that runs in the context of the test class so I can do setup specific to this test." (Fixtures in my case.)

#phpunit #php

Es war mir eine Ehre und eine Freude, über #PHP, #PHPUnit, Community und #OpenSource zu podcasten:

https://workingdraft.de/660/

#PHPUnit 12.1.4 has been released: https://github.com/sebastianbergmann/phpunit/releases/tag/12.1.4

#PHPUnit 11.5.19 has been released: https://github.com/sebastianbergmann/phpunit/releases/tag/11.5.19

#PHPUnit 10.5.46 has been released: https://github.com/sebastianbergmann/phpunit/releases/tag/10.5.46

#PHPUnit 9.6.23 has been released: https://github.com/sebastianbergmann/phpunit/releases/tag/9.6.23

#PHPUnit 8.5.42 has been released: https://github.com/sebastianbergmann/phpunit/releases/tag/8.5.42

Ok, so I'm confused about how @infection_php handles these specific mutators that are covered by tests:

#PHPUnit #InfectionPHP #PHP

Lesson learned from #phpunit codesprint:

When generating code coverage data in a immutable CI environment (e.g. #github #actions) with phpunit, make sure to restore the phpunit temp-folder, as otherwise it will be waaayy slower.

In collaboration with @localheinz I've build a small #github #actions utility workflow.

It describes how to segment a projects phpunit overall test-suite and distribute the load over parallel running github actions jobs

https://github.com/staabm/phpunit-github-action-matrix

#phpunit #codesprint

While sitting togehter with the #phpunit codesprint team in berlin, I am fixing #phpstan bugs to improve the phpunit use-cases of phpstan

https://github.com/sebastianbergmann/phpunit/issues/5886#issuecomment-2830109943