Last week we caught a bug caused by a security check on the users id (a Java Long) that was accidentally using == instead of .equals(). Since Java caches Long’s

Last week we caught a bug caused by a security check on the users id (a Java Long) that was accidentally using == instead of .equals(). Since Java caches Long’s between -127 and 128, == will pass for any ids <128, including those from our tests. Our QA stage only caught it because the tester happened to be a later stage employee, so had a user ID > 128.