So, I work in a medium sized team and earlier in this year, our team helped another that was behind in some tasks that all of us need to complete together.
After this, that team always asks for help from our team for untested things from their side and the worst part is whenever something breaks on their side, it breaks for a lot of people (like us) too, and they break a lot of stuff, simply not testing anything, no unit tests, no integration tests, nothing, they just throw broken shit out of the door.
This happens even to the things we made at their place, something’s up with our code? They changed it. It doesn’t seem to matter if it’s adding 2 lines to a sql query, they added an extra comma and didn’t test, they changed the batch processing? Now the process returns a broken json with different fields than the Enum expects. Yeah, they changed the value of the field that was ALREADY working for no reason and didn’t test it.
I’m pissed off, told my coworker that it’s their problem now, but the problems always come and the boss call us to help. This is very frustrating for us and for other teams too, even today another boss was talking about them breaking things in another system that we and they interact.
Their boss seemed to just want to give work for them, even with these problems coming back. The outsourced people work better than them, but you know, they are outsourced and the not so competent team is in house, so they can do nothing.
What can I do? Just saying no when the problems come? Talking to their boss?
The place I work has all that and even more, I think these kinds of errors that happen make upper management even more draconian with the rules (and we already have A LOT of rules).
how come that they can circumvent them?
merge is only allowed after passing the pipeline.
unittests have to be in place else merge is also cancelled.
they should simply dont get that far to make troubles for other parts of the codebase
Copilot writing all the unit tests and passing, while the unit tests don’t test anything or test the wrong thing. Passing the wrong thing to the services that consume their services, so it seems it works, but the service downstream just doesn’t work anymre.
for such things like shared documents/database entities also a shared test dataset should be available.
Then they cannot play around and modify those outputs anymore without noticing of others. (because their unittests would fail)
my assumption here is only an example. I dont know what youre dealing with.
While I understand the rant. And am on your side regarding those jerk moves. its a management issue. even when they do not act, its up to you to bring this to attention if this seriously conflicts with your work.
And in the long run its a win win for everyone.
edit: I am working myself in early development and despite being an engineer by background Im coding. So I know quite well how difficult it is to make it properly instead of quick and dirty.