ApproveJ v0.9.3 is out!
ApproveJ v0.9.3 is out!
π ApproveJ v0.9.3 is out!
π
/π introduces 16 new pre-defined Scrubbers for date/time strings
π fixes broken parsing if a date/time pattern contained a square bracket within an optional part
π https://github.com/mkutz/ApproveJ/releases/tag/v0.9.3
#approvaltesting #snapshottesting #java #kotlin #testing #jvm
π ApproveJ 0.8.6 was just published
ποΈ adds new review mechanism to automatically open a diff/merge tool if needed
thanks to all attendees of my session on #ApprovalTesting #verifyTesting #legacyTesting at #socrates NΓΌrnberg last week!
I really enjoyed the discussions during & after the talk!
The slides are online:
https://draptik.github.io/2024-09-swk-nbg-approval-testing/1
Thx #codecentric for sponsoring location & food & drinks
join me on a journey how testing helped our team port a #legacy app
https://www.meetup.com/de-DE/softwerkskammer-nuernberg/events/302057824/
#ApprovalTesting #dotnet
@emilybache 's newest video on dealing with #legacycode is really deep & high-end #tdd #ApprovalTesting !
I learned a lot, thanks Emily!
watch her video:
https://www.youtube.com/watch?v=cKj5cz8uAOM
I am playing with a git implementation in #rust. I currently have some tests using the Command API and assert. Since the test output gets large, I wonder whether I should use an `insta` or `lit` crate to test it.
Insta: I am already familiar with it, and it is just plain Rust code. The downside is that I find writing cli command in Rust pretty verbose.
Lit: I like the idea more but it seems unmaintained
Any thoughts?
Thanks to all attendees of my talk about 'Revitalizing Legacy Code using Approval Testing' at the MATHEMA-Campus: We had a great interactive session and I hope you enjoyed it as much as I did!
You can find the slides and the code examples on GitHub:
π https://draptik.github.io/2024-4-mathemacampus-approval-testing
#Verify #ApprovalTesting
special thanks to @simoncropp for the great support!