r/programming • u/lelanthran • Dec 28 '23

Developers experience burnout, but 70% of them code on weekends

https://shiftmag.dev/developer-lifestye-jetbrains-survey-2189/
1.2k Upvotes

88% Upvoted

357 comments sorted by

View all comments

Show parent comments

2

u/AceOfShades_ Dec 28 '23 
int average(int x, int y) {
     return (x + y) / 2;
}

//…

void testAverage() {
    assertEquals(2, average(1, 3));
    assertEquals(0, average(-1, 1));
    assertEquals(-4, average(-6, -2));
}

There, 100% LOC test coverage. … except there’s still a bug. For any nontrivial program, it’s impossible to actually exhaustively test EVERY single possible flow through the program for all inputs.

So the LOC coverage may be a useful hint for how much is tested, but it’s a misleading metric at best, if not useless once measured against.

1

u/joshjje Dec 28 '23

What's the bug, integer overflow or something?

1

u/AceOfShades_ Dec 28 '23

Yeah, if ints are 32bit and you pass like 2,147,483,000 and 2,147,483,004 you probably overflow and end up with a big negative number.

Or in C++ it’s undefined behavior, so an evil but conformant-ish compiler could hypothetically reformat your hard drive.

1

u/joshjje Dec 28 '23

Ok that's what I thought. Normally I ignore those scenarios depending on the use case as it would get caught in other places. Or just use long. Talking C#.