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?
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
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