Finding a failing test ๐Ÿšจ, coming back from the โ˜•๏ธ break, feels just so โœ… .

- I know where I left off
- I know what to continue with
- I get back into the flow within seconds
- no need to search and analyze the git history
- it ๐Ÿ’ก enlightens me and lets me continue where i left off

also when doing hashtag#PHP ๐Ÿ˜Ž

#unittest #testing #tdd #engineering #workflow #productive

God, LLM's write the weirdest and worst unit tests. Why do I gotta review this slop.

#LLM #unittest

I was about to request jokingly an assertRoughlyEquals() method in #phpunit to avoid errors like "Failed asserting that 5.656000000000001 is identical to 5.656" when testing with floats.

Then I realized it already exists ! ๐Ÿ˜‚
https://docs.phpunit.de/en/12.5/assertions.html#assertequalswithdelta

Handy !

#php #unittest

1. Assertions โ€” PHPUnit 12.5 Manual

I built something useful with the #erlang programming language: a tool to determine whether data found in files spat out by a generator contains information that matches contents of a database. This is used to #unittest the generator. The client for which this got built didn't have automated unit tests for that yet. This should help detect regression bugs caused by maintenance.

Code review complete. Time to merge.

Final damage:

[native-aot cdfb42b2] Add Native AOT support
Date: Wed Feb 25 11:16:49 2026 -0800
856 files changed, 33149 insertions(+), 14167 deletions(-)

#DotNet #UnitTest #NativeAOT

New option coming for the xunit3 template: "--native-aot".

This will only be available for C# projects, since Native AOT is only implemented for C#. #DotNet #UnitTest #NativeAOT

They may take longer to builder, but they're definitely faster to run. ๐Ÿ˜„ #DotNet #UnitTest #NativeAOT
I'm positive the code generation has holes in it, despite my extensive attempt to ensure I covered all my bases, but... I think I'm ready the merge `native-aot` into `rel/4.0.0` and maybe push a pre-release build soon. #DotNet #UnitTest #NativeAOT

The existing xUnit.net analyzers that are errors are helping define the most important set of "did I remember to test for this?" in the code generators, because they almost all end up creating generated code that won't compile (e.g., m Member data pointing at a non-public member). Almost all of the rest inform what conditions need to be validated in the generated code (e.g. incorrect number of values in a data row vs. number of parameters to the test method).

#DotNet #UnitTest #NativeAOT

Still don't have caching wired up, and I don't think I'm gonna bother, because things definitely got faster.

Also, count-wise I clearly have to make a pass to determine if there are more current "reflection only" tests that need AOT backfills.

Also need to fix an issue where I'm calling tests multiple times if they're defined in a partial across separate files.

#DotNet #UnitTest #NativeAOT