LIST
" The vocabulary for talking about this soon gets messy - all sorts of words are used: stub, mock, fake, dummy. " Test Double the generic term for any kind of pretend object used in place of a real object for testing purposes. five particular kinds of double (1) Dummy objects passed around but never actually used. eg. fill parameter lists (2) Fake objects working implementations shortcut which makes them not suitable for production eg....
(src: Testing of Microservices - Spotify Engineering _ Spotify Engineering)
I’ve been struggling to use this principle in practice. I’ve read about it, heard it mentioned, heard it discussed and explained. But it only clicked when I stumbled into this example at work: We needed to sync certain tasks from one tool to the other. But we needed to make sure that tasks were only sent once. There was to be no duplication at the receiving end. We also wanted to show a count of the tasks that were synced in the stats...