this post was submitted on 28 Jul 2025
26 points (90.6% liked)
Programming
21924 readers
684 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.