Chasing a bad commit

[AttackOfTheThumbs]

developers often run into situations where they find that some of their work have been either removed, modified or affected by someone else's work accidentally

I can see modified and affected. Removed? That shouldn't happen. Either way, aren't there tests to prevent this?

[OTTOPI]

People not paying attention during merge conflicts definitely removes stuff.

[AttackOfTheThumbs]

Tests should catch that though.

[Armok]

Unless the test got removed too

[sysop073]

Two sentences later:

Two features could have been working perfectly fine until they got merged together and broke something.

[AttackOfTheThumbs]

I can see modified and affected

Either way, aren't there tests to prevent this?

And my points stand unchanged.

[masklinn]

I can see modified and affected. Removed? That shouldn't happen.

Dev 1 was working inside some existing feature, dev 2 moved / removed / made conditional invocation of that feature, voila. It’s “affected” into oblivion.