Jest tests are essential for developing Lightning Web Components (LWC) because they allow developers to ensure the quality and correctness of their components in isolation from the rest of the application. Reason A is incorrect because testing non-public properties breaks encapsulation and is considered bad practice. B is correct because Jest tests can simulate user interactions with the component, such as clicking buttons or entering text, to ensure it behaves as expected. C is correct as well because Jest tests can confirm that the component renders the expected DOM output, which is crucial for ensuring that the HTML structure of the component is accurate. D is not the best choice since Jest is more suited for testing components in isolation rather than how multiple components interact; integration tests are more appropriate for that. Lastly, E is correct because Jest tests can verify that events are fired at the appropriate times, which is a critical part of the component's interaction with the rest of the application.
References
Jest Testing: Lightning Web Components Testing
Jest Testing Best Practices: Lightning Web Components Jest Best Practices