Time: 0:00
Test a custom input to verify an edge case (e.g. empty lists, negative numbers, duplicates).
This bug belongs to the logic errors pattern
The wrong operator, an inverted condition, a formula the right way round but backwards.
What went wrong: The == operator checks for reference equality for objects, and while Java caches Integer objects in the range -128 to 127, values outside this range are not guaranteed to be the same object even if they are equal in value.
The fix: Use the equals method for objects to ensure value equality is checked. However, in this case, using == for primitive int types is correct, and the issue lies in the assertion for values outside the cached range.
Remember: Be aware of Java's Integer cache and the difference between == and equals for objects.
The pattern behind it: logic errors.
Paste this into any web page or blog post. Visitors fix the bug right there, in their browser.
<iframe src="https://trybughunt.com/embed/1129ab38-cf6d-4c57-bee8-dca7b647c8d2" title="Debugging challenge: Equality Check Fails for Certain Integer Values" width="100%" height="580" loading="lazy" style="border:1px solid #d4d4d8;border-radius:12px;max-width:760px"></iframe>
<p style="font-size:14px">Debugging challenge from <a href="https://trybughunt.com/challenges/1129ab38-cf6d-4c57-bee8-dca7b647c8d2">TryBugHunt</a></p>