I have been learning TDD over the past month or so on the Laravel/Vue stack. I ran through the fantastic vue exercise at outsidein.dev/ and they teach jest for unit testing and cypress for e2e so I have been sticking with them. However, at work we use docker and we haven't been able to get the cypress runner UI working so I have been stuck with their ci cli runner which sucks and so I'm about to start looking into laravel Dusk.
In my company the whole testing paradigm is reserved for the super advanced programmers (which is backwards, I know - TDD should be how we teach our juniors from the start) and it takes a long time to learn the APIs and setup processes for each of those testing suites so I would say the complexity is a real barrier to providing to our clients what is quite an essential part of the software cycle - built in tests.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I have been learning TDD over the past month or so on the Laravel/Vue stack. I ran through the fantastic vue exercise at outsidein.dev/ and they teach jest for unit testing and cypress for e2e so I have been sticking with them. However, at work we use docker and we haven't been able to get the cypress runner UI working so I have been stuck with their ci cli runner which sucks and so I'm about to start looking into laravel Dusk.
In my company the whole testing paradigm is reserved for the super advanced programmers (which is backwards, I know - TDD should be how we teach our juniors from the start) and it takes a long time to learn the APIs and setup processes for each of those testing suites so I would say the complexity is a real barrier to providing to our clients what is quite an essential part of the software cycle - built in tests.