When I have to ask the same person in the team for the hundredth time why they didn't run the unit tests before pushing 😞

Then eventually get them to setup system that prevents merging with broken tests themselves, but they do it in such a way that still lets them get away with pushing broken tests 😡

Yeah, sure. Send in your code for review with THE UNIT TESTS YOU WROTE FOR YOUR CODE FAILING!

I've never written any unit tests for any apps/programs I've developed.

I would tell myself, this time you're going to create some and be a better developer by doing so. I end up just creating the file and that's it.

Most of the bugs are discovered during the user testing phase so I always end up being lazy writing unit tests.

I write very defensive code though so that helps a little but all in all, it's a very bad habit that I need to snap out of

I really need help. We are doing some interface files, something like C header files and configurations.

Management is aware of the "unittesting" buzz words and expects me to write unit tests on "header" and configuration files....

I tried to explain that there are no units to be tested, asked which units should be tested but in the end....

What does it actually mean to test definitions of structures, classes and methods?!

Android Studio 3.2b4 once again regressed on "No tests found" bug for Kotlin projects.

I guess someone at big G decided to "comment out failing tests for now and come back to it before the release"

I feel like this rant should be riddled with profanity but at this point I'm not even angry just very disappointed 😥