Programming

24072 readers

155 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev

Testing Side Effects Without the Side Effects (lackofimagination.org)

submitted 1 day ago by Aijan@programming.dev to c/programming@programming.dev

6 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] magic_lobster_party@fedia.io 7 points 1 day ago (1 children)

This only checks that functions are called in the right order. Not that the functions are doing the right thing or if the functions are called with the correct arguments. Quite pointless testing IMO.

For example, it won’t capture cases where cmdChargeCreditCard returns a payment ID that exists for cmdCompleteOrder to use.

Set up an in-memory database, or test against a real database. You don’t test side effects by pretending that the side effects are correct.

[–] Aijan@programming.dev 1 points 1 day ago

You can still test the functions individually or run the entire flow against a test database, but without an effect system like this, it's very hard to test business logic in isolation.