Adding to those points, it’s important to remember that Thread.sleep() should never be your first choice in Selenium automation because it introduces fixed delays that can either waste time or cause flaky tests.
Instead, use dynamic waits wherever possible, but keep Thread.sleep() handy for those rare situations — like waiting for visual effects or non-DOM changes where Selenium’s usual wait methods don’t work well. It’s more like a last-resort tool when you need a guaranteed pause.