Write unit tests should be as fun as writing your feature code, no matter which language you're using, it's all code at the end of the day.
...
For further actions, you may consider blocking this person and/or reporting abuse
You need to consider the problems you're trying to solve with unit tests.
These may be:
Once you understand what problem you're trying to solve, you can try to figure out how well unit testing achieves these for you, or if there a better alternatives.
But if you don't know why you're doing unit testing, except that TDD is good, then you won't be able to make a reasoned assessment, since your position will be ideological.
So, I suggest focusing on the actual problems rather than on a particular approach.
Thanks for enriching the discussion, completely valid points. I wrote this more because of past experiences and talks with friends. Unfortunately, some projects nowadays still don't have a good unit test base. I'm lucky enough to have it working quite well in my projects.
Writing tests early helps a ton. It doesn't have to follow TDD to a T, but often we are writing code, then checking the output of a bunch of things. Unit Testing is an amazing tool to help speed up this process and give us confidence in future releases.
Stop manually checking things and just write a test already!
I guess it's broken because there was a rushed sprint and someone forgot to update test cases
In my experience this is one of the biggest causes for tests not getting written. Rushed feature pushes. So what gets left out? Tests
Or it's not engrained into team culture.
Couldn't agree more ;)
I find writing tests to be quite enjoyable, mostly unit tests because of the fast feedback and the lack of dependencies I have to mess with. I use unit tests mostly for checking things work, being sure on edge cases and documentation. The thing that ruins the fun of writing tests is TDD, so I write tests after the code and that works well for me.
Having too much reliance on unit tests is the pitfall here, they're usually brittle and make refactoring more expensive, which will often be mocks being wrong after the change.
So... why is unit test culture broken?
Thanks Ben, well in my point of view, there're a number of things... to point out a few I would say:
Those are some that I can tell, make sense?
I guess you're mostly saying that it's a problem because people don't do them? I thought from the title you meant that people were doing unit tests but something was wrong with the way they were done.
Wow, got it... yes I meant to say more about the culture of doing it itself.
Its not totally broken, Its followed by many testers. There are some rules and techniques to follow. May be this will be helpful. dev.to/campkathleen3/explain-unit-...
Great man.
It’s about culture