It’s strangely satisfying when the “this will probably never happen” test case finds a problem during development.
I had tests for deleting that were like
- create item a
- create item b
- delete item a via the code under test
- assert item a is gone
- assert item b is still there
I thought maybe the whole bit with item b was excessive, but sure enough one day I accidentally fucked something up and deleted all the items, and the test pointed it out before the bad code left my local machine.
the autistic overthinking the unit tests
overthinked squared
Think of it as a function you can unleash on others…
what if someone tries to input a cat to this function?
Autist 🙂↔️
Autest 🙂↕️
Ok, well, if you ever come across a test framework named AuTest, you can blame me, because I’m stealing the shit out of that.
Por que no los dos?
Z – Zero O – One M – Many (or More complex) B – Boundary Behaviors I – Interface definition E – Exercise Exceptional behavior S – Simple Scenarios, Simple Solutions
Use triple backticks instead of one if you are trying to get monospace syntax
Bless. Also please dont peel my face off for that mistake :p
Sorry, the face scalpers are already on their way. Nothing we can do