Java Interview Questions

Difference between HashMap, LinkedHashMap and TreeMap?

How do you find duplicate characters in a String using Java 8 Streams?

Stream the chars, group by identity with counting, filter entries with count > 1.

Abstract class vs interface — which do you use in your framework and why?

Abstract class for shared state + partial implementation (BasePage, BaseTest); interface for capability contracts (Reportable, DataProvider strategy).

How do you choose between ArrayList, LinkedList, HashMap and HashSet in test code?

ArrayList for ordered, index-accessed data, HashMap for key lookups such as test data by id, HashSet for uniqueness checks, LinkedList almost never in test frameworks.

How does HashMap work internally, and why must hashCode and equals agree?

HashMap stores entries in buckets chosen by hashCode; equals resolves collisions inside a bucket. If two equal objects return different hash codes they land in different buckets and lookups silently fail.

Interface vs abstract class — how does that decision show up in a test framework?

Abstract classes share state and common behaviour (BasePage, BaseTest); interfaces declare capability contracts (Reportable, DriverProvider) and allow multiple inheritance of type.

How do you use Java streams to prepare and verify test data?

Streams turn filter/map/collect chains into one readable line — building payload lists, extracting a column of a table, or asserting a property holds for every row.

How do you make WebDriver thread-safe for parallel execution?

Keep the driver in a ThreadLocal inside a DriverManager, create it in a @BeforeMethod and always remove() it in @AfterMethod to avoid leaking between threads.

How should exceptions be handled in an automation framework?

Never swallow exceptions in a try/catch that returns false — wrap them in a meaningful custom exception with context so the report shows why the step failed.

What is encapsulation, and why does it matter in Java?

encapsulation is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply encapsulation in a production Java project?

Apply encapsulation through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is inheritance, and why does it matter in Java?

inheritance is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply inheritance in a production Java project?

Apply inheritance through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is polymorphism, and why does it matter in Java?

polymorphism is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply polymorphism in a production Java project?

Apply polymorphism through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is abstraction, and why does it matter in Java?

abstraction is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply abstraction in a production Java project?

Apply abstraction through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is interfaces versus abstract classes, and why does it matter in Java?

interfaces versus abstract classes is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply interfaces versus abstract classes in a production Java project?

Apply interfaces versus abstract classes through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is String immutability, and why does it matter in Java?

String immutability is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply String immutability in a production Java project?

Apply String immutability through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is equals and hashCode, and why does it matter in Java?

equals and hashCode is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply equals and hashCode in a production Java project?

Apply equals and hashCode through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is collections hierarchy, and why does it matter in Java?

collections hierarchy is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply collections hierarchy in a production Java project?

Apply collections hierarchy through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is ArrayList versus LinkedList, and why does it matter in Java?

ArrayList versus LinkedList is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply ArrayList versus LinkedList in a production Java project?

Apply ArrayList versus LinkedList through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is HashMap internals, and why does it matter in Java?

HashMap internals is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply HashMap internals in a production Java project?

Apply HashMap internals through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is sets, and why does it matter in Java?

sets is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply sets in a production Java project?

Apply sets through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is checked and unchecked exceptions, and why does it matter in Java?

checked and unchecked exceptions is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply checked and unchecked exceptions in a production Java project?

Apply checked and unchecked exceptions through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is try-with-resources, and why does it matter in Java?

try-with-resources is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply try-with-resources in a production Java project?

Apply try-with-resources through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is generics, and why does it matter in Java?

generics is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply generics in a production Java project?

Apply generics through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is streams, and why does it matter in Java?

streams is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply streams in a production Java project?

Apply streams through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is lambda expressions, and why does it matter in Java?

lambda expressions is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply lambda expressions in a production Java project?

Apply lambda expressions through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is Optional, and why does it matter in Java?

Optional is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply Optional in a production Java project?

Apply Optional through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is multithreading, and why does it matter in Java?

multithreading is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply multithreading in a production Java project?

Apply multithreading through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is synchronization, and why does it matter in Java?

synchronization is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply synchronization in a production Java project?

Apply synchronization through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is concurrent collections, and why does it matter in Java?

concurrent collections is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply concurrent collections in a production Java project?

Apply concurrent collections through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is records, and why does it matter in Java?

records is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply records in a production Java project?

Apply records through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is sealed classes, and why does it matter in Java?

sealed classes is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply sealed classes in a production Java project?

Apply sealed classes through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is garbage collection, and why does it matter in Java?

garbage collection is a core Java concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply garbage collection in a production Java project?

Apply garbage collection through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.