aaaarc
This is what writing useful tests mean, from a client perspective I just want to understand what's valid and what's invalid.
Also useful to make sure we fixed specific scenario bugs.
I've seen a lot of people doing things wrong but we can summarise in two cases: - "We've got 100% coverage, it must mean we've got no bugs, right?" - We've got tests covering happy path, everything else is tested manually. It takes forever and it's not shared anywhere, but "trust me" I've tested this.
I still get triggered when I hear the Nokia ringtone.
First, we were all offered good rates for on-call support so we had plenty of people who wanted in so I wouldn't do any support and leave it to the guys who wanted the money.
Then some of the guys left the team and got replaced, they offered a different deal to the new guys, less lucrative, therefore, they didn't want to do it.
As a senior I had to start doing support, I thought the extra money would maybe make me feel ok, then we had less and less people on rota so I was doing support most weekends which started affecting my marriage.
I escalated the issue (again), nothing was done, one month later I gave my notice on the highest paying and best dev job I had.
I was on-call for full month straight during my notice, that's how bad it got. And I steer clear from dev with support roles now.