JavaScript Interview Questions

Explain async/await, promises and the event loop for test code.

Explain the JavaScript event loop and how it affects asynchronous test code.

The event loop lets a single-threaded JS runtime handle async operations by pushing callbacks onto a queue that runs only after the call stack is empty, with microtasks (promises) draining before macrotasks (setTimeout).

Compare Promises with async/await — when would you choose one over the other in test automation?

Async/await is syntactic sugar over Promises that reads like synchronous code; Promises' .then chaining is still useful for running independent async operations in parallel with Promise.all.

What is a closure and where have you used one in a test automation framework?

A closure is a function that retains access to its enclosing scope's variables even after that outer function has returned, commonly used to create private state like counters or configured helper functions.

How does 'this' behave differently in regular functions vs arrow functions, and why does it matter in test hooks?

Regular functions get 'this' determined by how they're called (dynamic binding), while arrow functions inherit 'this' lexically from their enclosing scope at definition time.

Which array methods do you rely on most for shaping test data, and how do map/filter/reduce differ?

map transforms each element into a new array of the same length, filter keeps only elements matching a predicate, and reduce folds the array into a single accumulated value.

How do you properly handle and assert errors in asynchronous test code?

Wrap awaited calls in try/catch to assert on thrown errors, or use your test framework's rejection matcher like expect(promise).rejects.toThrow() instead of manually catching.

What's the difference between == and ===, and where has loose equality caused a subtle test bug?

== performs type coercion before comparing while === compares both type and value without coercion, so === is almost always the safer choice in assertions.

What is execution context, and why does it matter in JavaScript?

execution context is a core JavaScript concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply execution context in a production JavaScript project?

Apply execution context 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 scope chain, and why does it matter in JavaScript?

scope chain is a core JavaScript concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply scope chain in a production JavaScript project?

Apply scope chain 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 closures, and why does it matter in JavaScript?

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

How would you apply closures in a production JavaScript project?

Apply closures 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 hoisting, and why does it matter in JavaScript?

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

How would you apply hoisting in a production JavaScript project?

Apply hoisting 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 temporal dead zone, and why does it matter in JavaScript?

temporal dead zone is a core JavaScript concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply temporal dead zone in a production JavaScript project?

Apply temporal dead zone 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 event loop, and why does it matter in JavaScript?

event loop is a core JavaScript concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply event loop in a production JavaScript project?

Apply event loop 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 microtasks and macrotasks, and why does it matter in JavaScript?

microtasks and macrotasks is a core JavaScript concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply microtasks and macrotasks in a production JavaScript project?

Apply microtasks and macrotasks 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 promises, and why does it matter in JavaScript?

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

How would you apply promises in a production JavaScript project?

Apply promises 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 async and await, and why does it matter in JavaScript?

async and await is a core JavaScript concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply async and await in a production JavaScript project?

Apply async and await 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 Promise.all and allSettled, and why does it matter in JavaScript?

Promise.all and allSettled is a core JavaScript concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply Promise.all and allSettled in a production JavaScript project?

Apply Promise.all and allSettled 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 prototype chain, and why does it matter in JavaScript?

prototype chain is a core JavaScript concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply prototype chain in a production JavaScript project?

Apply prototype chain 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 this binding, and why does it matter in JavaScript?

this binding is a core JavaScript concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply this binding in a production JavaScript project?

Apply this binding 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 arrow functions, and why does it matter in JavaScript?

arrow functions is a core JavaScript concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply arrow functions in a production JavaScript project?

Apply arrow functions 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 destructuring, and why does it matter in JavaScript?

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

How would you apply destructuring in a production JavaScript project?

Apply destructuring 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 spread and rest syntax, and why does it matter in JavaScript?

spread and rest syntax is a core JavaScript concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply spread and rest syntax in a production JavaScript project?

Apply spread and rest syntax 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 map filter and reduce, and why does it matter in JavaScript?

map filter and reduce is a core JavaScript concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply map filter and reduce in a production JavaScript project?

Apply map filter and reduce 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 deep versus shallow copy, and why does it matter in JavaScript?

deep versus shallow copy is a core JavaScript concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply deep versus shallow copy in a production JavaScript project?

Apply deep versus shallow copy 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 modules, and why does it matter in JavaScript?

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

How would you apply modules in a production JavaScript project?

Apply modules 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 error handling, and why does it matter in JavaScript?

error handling is a core JavaScript concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply error handling in a production JavaScript project?

Apply error handling 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 debouncing and throttling, and why does it matter in JavaScript?

debouncing and throttling is a core JavaScript concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply debouncing and throttling in a production JavaScript project?

Apply debouncing and throttling 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 chaining, and why does it matter in JavaScript?

optional chaining is a core JavaScript concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply optional chaining in a production JavaScript project?

Apply optional chaining 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 nullish coalescing, and why does it matter in JavaScript?

nullish coalescing is a core JavaScript concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply nullish coalescing in a production JavaScript project?

Apply nullish coalescing 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 memory leaks, and why does it matter in JavaScript?

memory leaks is a core JavaScript concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply memory leaks in a production JavaScript project?

Apply memory leaks 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.