Expecty macro libary has been historically maintained by @Baccata, me, and Eugene Yokota, the current maintainer of the fork.
The code from it has been inlined and improved in the Verify testing framework maintained by Eugene.
Inlining the dependency makes release cycles obviously easier.
I believe it's time we design the assertion macros from scratch, as part of this repo, not separate dependency, and address multiple issues related to how Expecty renders assertion failures. See screenshot for an example of an unusable output.
Once we inline the dependency, this issue can be broken down into actionable, smaller issues.
Expecty macro libary has been historically maintained by @Baccata, me, and Eugene Yokota, the current maintainer of the fork.
The code from it has been inlined and improved in the Verify testing framework maintained by Eugene. Inlining the dependency makes release cycles obviously easier.
I believe it's time we design the assertion macros from scratch, as part of this repo, not separate dependency, and address multiple issues related to how Expecty renders assertion failures. See screenshot for an example of an unusable output.
Once we inline the dependency, this issue can be broken down into actionable, smaller issues.