Hello, friends! I’ve been thinking back on my career recently, which I’ve had plenty of time to do, considering that I am exploring creative outlets like blogging, and that I’m cu…
I didn’t read the full post. I stopped after the author complained about test coverage.
If it takes you twice as long to write your tests as it does to implement the feature, the failure isn’t on the requirements to write the test, it’s somewhere else in the chain. Is the framework not conducive to testing? His reference to their design library suggests that might be the case.
I’m all for skipping tests on frontend, and even some on backend for non-critical logic. But I’ve seen simple human error that would have been caught by testing cause significant harm.
My coworkers ask me how I manage to write code that rarely has issues and I tell them I don’t, it has issues, then I test it, I facepalm, and I fix it.
I didn’t read the full post. I stopped after the author complained about test coverage.
If it takes you twice as long to write your tests as it does to implement the feature, the failure isn’t on the requirements to write the test, it’s somewhere else in the chain. Is the framework not conducive to testing? His reference to their design library suggests that might be the case.
I’m all for skipping tests on frontend, and even some on backend for non-critical logic. But I’ve seen simple human error that would have been caught by testing cause significant harm.
My coworkers ask me how I manage to write code that rarely has issues and I tell them I don’t, it has issues, then I test it, I facepalm, and I fix it.