this post was submitted on 09 Aug 2024
33 points (100.0% liked)
Programming
18304 readers
139 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
As the boundary between unit tests and integration tests has never be been smaller. And mocks still suck. And container first development leads to easier container deployments. And containers offer a very easy development environment setup. And containers are immutable, or at least reproducable, meaning future compatibility is much more dependable. Ever tried to run php5 unit tests any more?
Ohhhhh nononono, I am NOT besmirching containers.
I am merely pointing out that unit tests come before any deployment what so ever. If you're having mock issues, you are writing your code wrong. Even basic OOP and encapsulation practices should keep your various classes/objects from becoming too intertwined to easily mock.
PHP? Oh... oh that explains a lot... You sweet, sweet summer child.
Yeah, testing in containers I think docker compose could do with some more support personally. Not sure what, but they have deploy and build blocks, I'd like to see a testing block and a
docker compose test