Additional Question on Unit Test

How can you test asynchronous behavior in React components?

How do you handle testing components with context providers?

What’s the difference between getBy, queryBy, and findBy queries in React Testing Library?

• getBy: Throws an error if no elements or multiple elements are found. Use when you expect exactly one element to be present.
• queryBy: Returns null if no elements are found, without throwing an error. Use when you expect an element might not be present.
• findBy: Returns a promise that resolves when the element is found or rejects if the element is not found within a timeout. Use for asynchronous behavior.

How do you test components that use useEffect?

How do you mock module dependencies in tests

How do you test a component’s CSS class changes?

How do you test user interactions with form elements?

How do you test conditional rendering?

What are some common pitfalls in React unit testing?

• Testing implementation details: Focus on the behavior rather than the internal structure
• Not cleaning up between tests: Ensure that tests do not interfere with each other.
• Overusing snapshot tests: Snapshots can become outdated and may not provide much value for components with frequent changes.

How do you handle component performance in tests?

For performance concerns, test how components handle large data or complex rendering scenarios. Use tools like React Profiler in development to analyze performance and ensure tests don’t inadvertently slow down your test suite.