Introduction
Handling login smartly saves time by avoiding repeated slow login steps in tests.
When many tests need a logged-in user to start.
When login takes a long time or has complex steps.
When you want tests to run faster and more reliably.
When you want to avoid hitting login limits or captchas.
When you want to focus tests on main features, not login.