That's a great point Ravern, and I feel you - I've had the same thing. I think that you don't need to unit test things that are:
Features of an underlying dependency
Basic CRUD pipelines which don't alter or transform the data
But anything in your solution which is unique or original could be unit tested. For example:
Do you have data transfer objects which construct on top of data from another source? Test that they instantiate with the expected values
Do you parse/process/transform API data? Unit test your assumptions about that
Straightforward API projects often do some of the above.
That said, unit testing is a helper, not a law! Test what it's helpful to test. Your end-to-end testing sounds like it provides a lot of value, and perhaps in many cases that's all you need!
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.
That's a great point Ravern, and I feel you - I've had the same thing. I think that you don't need to unit test things that are:
But anything in your solution which is unique or original could be unit tested. For example:
Straightforward API projects often do some of the above.
That said, unit testing is a helper, not a law! Test what it's helpful to test. Your end-to-end testing sounds like it provides a lot of value, and perhaps in many cases that's all you need!