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: In Java, the == operator compares object reference identities (memory addresses), not the actual character contents of the strings. Strings constructed at runtime or dynamically are distinct objects, so == evaluates to false.
The fix: Use "admin".equals(role) to perform content comparison, which also protects against null pointer exceptions if role is null.
Remember: Always compare Strings in Java using .equals(), never ==. Put the string literal first ("admin".equals(role)) to avoid NullPointerException.
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/04381d64-b996-4b63-aab7-7780e6f8e2c5" title="Debugging challenge: String equality comparison with == operator" 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/04381d64-b996-4b63-aab7-7780e6f8e2c5">TryBugHunt</a></p>