- Best Practice: Avoid Dependencies between Tests to Run Tests in Parallel
- Best Practice: Avoid External Test Dependencies
- Best Practice: Keep Functional Tests Separate from Performance Tests
- Best Practice: Don't Use Brittle Locators in Your Tests
- Best Practice: Use Build IDs, Tags, and Names to Identify Your Tests
- Best Practice: Use Explicit Waits
- Best Practice: Use the Latest Version of Selenium Client Bindings
- Best Practices: Use Small, Atomic, Autonomous Tests
- Best Practice: Have a Retry Strategy for Handling Flakes
- Best Practice: Use Environment Variables for Authentication Credentials
- Best Practice: Use Breakpoints to Diagnose Flaky Tests
- Best Practice: Use New Accounts For Each Test
- Best Practice: Avoid Leakage of Credentials
- Best Practice: Be Aware of the Load on Your Servers
- Best Practice: Imperative v. Declarative Testing Scenarios
- Best Practice: Use Maven to Manage Project Dependencies
- _best_practices_sauce_options
Overview
Content Tools