The devs listened <3 I complained for quite a while that writing tests for @phylaxsystems assertions had really bad devex. External feedback verified this, and fixing the devex was prioritized. The fix is a simpler and more powerful testing interface!

Instead of first setting up an assertion with a confusing label and abi.encode and then use the convoluted cl.validate to craft the tx to run the assertion against, we now have one simple cheatcode that sets up the assertion to be run against the next tx

Only one assertion function is run against a transaction. Before all assertion functions that a tx triggered would be run and it was difficult to test specific assertion functions.

cl.validate() didn't persist state changes caused by the tx it validated. In the new interface, txs are executed as expected and state is updated, which means you can verify that state changes happened as expected and write more complete tests.

Lastly, you can now match against exact revert reasons, which makes it much easier to write tests for specific edge cases that fail a particular check in the assertion function.

As someone who has written a lot of assertion tests so far, I find this update amazing. I have to write less code, and I have more control and functionality - devex as it should be. The Phylax Team is on 🔥