While writing code, it will be in a nonsensical state for most of the time until you complete a chunk. What additional value does running the unit tests continuously bring over just running it when you complete a chunk of code?
this post was submitted on 16 Mar 2025
16 points (100.0% liked)
Programming
19122 readers
98 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
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 [email protected]
founded 2 years ago
MODERATORS
That's a good question. For me it's not really about it running all the time but it's about not having to spend any mental effort to switching "mode"and running the tests. With this and the IDE integration it really makes testing a first class activity. I think wallaby that I linked has some videos of the experience which might make more sense than my words.
Most continuous test runners don't actually run on every key stroke but wait until it's syntactically valid. It's also common for them to do some smart diff and only re-run a subset of the tests.