A collision occurs when distinct keys map to the same hash-table slot, so a table needs a collision-resolution strategy.
How to reason about it
Start by identifying the state the method maintains and the operation that changes it. Then trace one small input by hand. This separates the invariant that makes the method correct from implementation details such as arrays, pointers, counters, or protocol messages.
Worked example
With separate chaining, keys that map to bucket two share that bucket; with linear probing, a later free slot is searched.
Write down the state before and after each step. For a larger input, repeat the same transition rather than guessing from the final output. That habit makes edge cases visible and gives you a concrete basis for testing.
Trade-offs and common mistakes
A hash value is not a unique identifier, and collision handling is part of the table's correctness.'
Choose this technique when its assumptions match the problem. State those assumptions explicitly, test an empty or boundary input, and compare the cost of the operation you perform most often with the memory or setup cost it introduces.
Takeaway
Hash Collisions: Chaining and Open Addressing becomes easier to use once its invariant, input assumptions, and failure cases are clear. A small worked example is a useful first test; measurements and proofs should follow when the system grows.