Backend colleague : the API is online. It's tested and working, you can start the dev.

Me trying to manually call the API with all the fields pre validated : "error : invalid fields"

EVERY. FUCKING. TIME !

To all the backend developers : we are NOT your personal testers, and we are NOT supposed to clean your mess because you're too lazy to FUCKING TEST THE HAPPY PATH!!!

Thank you for your consideration.

Maybe start the conversation next time like this:

Ok. If you want to talk, fine.

We can have nice and long conversations.

Even about feelings.

I can scream and insult you if that tickles ya fetish

But please, stop giving me untested shit as a way to get my attention, it's not okay?

@IntrusionCM I just don't get why this is even happening to be honest. I'm mostly frontend but every time I write an api, I always test the happy path. Always.

This is basic respect to my co-workers and to future me.
The guy is a senior developer, I don't know how to start a conversation about this without making him feel personally attacked...

(BTW I have a good relationship with the guy overall)

@react-guy hmmm.

"Without feeling personally attacked"...

If his first reaction in a 4 eyes talk (private conversation) is to take it personal, then this guy is a fuckwad.

I know many seniors suffer from an God Complex or "L'etat c'est moi" personality, but this isn't okay at work.

They're paid for doing exactly that. Their fucking job.

I guess the question: "Do you utilize testing during your API creation in the backend team?" isn't personal.

Yes... You will have to deliver the message "I noticed whenever I was sent an link to an finished API, I had to plan extra time as it just didn't work - seems like it wasn't properly tested and finished, sadly. Do you know why?' sooner or later. As long as u stay calm and rational, it's a valid question.

Hard to believe someone would just develop an API without testing it constantly during development. You obviously need to keep shooting requests while you develop something, so I assume it had to keep passing for the dev.

The issue is the lack of written integration tests, because even if things worked at the start, doesn't mean it works by the end!

This should be part of the "Definition of Done" for BE, things should be covered by tests. For APIs integration tests have the best value, Unit tests tend to test boilerplate with modern APIs, so barely useful...

But even with happy path, there might be a leak they honestly missed or maybe an undocumented resource you need first before calling.

In short, BE dev can quickly turn into a mess, especially with deadlines

It always happen.. what fuck why