From runnings tests in parallel to how to use small, atomic, autonomous tests check out this comprehensive guide on best practices for running tests.
Avoid External Test Dependencies
| Include Page |
|---|
| DOCS:Best Practice: Avoid External Test Dependencies |
|---|
| DOCS:Best Practice: Avoid External Test Dependencies |
|---|
|
Avoid Dependencies between Tests to Run Tests in Parallel
| Include Page |
|---|
| DOCS:Best Practice: Avoid Dependencies between Tests to Run Tests in Parallel |
|---|
| DOCS:Best Practice: Avoid Dependencies between Tests to Run Tests in Parallel |
|---|
|
Don't Use Brittle Locators in Your Tests
| Include Page |
|---|
| DOCS:Best Practice: Don't Use Brittle Locators in Your Tests |
|---|
| DOCS:Best Practice: Don't Use Brittle Locators in Your Tests |
|---|
|
Have a Retry Strategy for Handling Flakes
| Include Page |
|---|
| DOCS:Best Practice: Have a Retry Strategy for Handling Flakes |
|---|
| DOCS:Best Practice: Have a Retry Strategy for Handling Flakes |
|---|
|
Keep Functional Tests Separate from Performance Tests
| Include Page |
|---|
| DOCS:Best Practice: Keep Functional Tests Separate from Performance Tests |
|---|
| DOCS:Best Practice: Keep Functional Tests Separate from Performance Tests |
|---|
|
Use Build IDs, Tags, and Names to Identify Your Tests
| Include Page |
|---|
| DOCS:Best Practice: Use Build IDs, Tags, and Names to Identify Your Tests |
|---|
| DOCS:Best Practice: Use Build IDs, Tags, and Names to Identify Your Tests |
|---|
|
Use Environment Variables for Authentication Credentials
| Include Page |
|---|
| DOCS:Best Practice: Use Environment Variables for Authentication Credentials |
|---|
| DOCS:Best Practice: Use Environment Variables for Authentication Credentials |
|---|
|
Use Explicit Waits
| Include Page |
|---|
| DOCS:Best Practice: Use Explicit Waits |
|---|
| DOCS:Best Practice: Use Explicit Waits |
|---|
|
Use the Latest Version of Selenium Client Bindings
| Include Page |
|---|
| DOCS:Best Practice: Use the Latest Version of Selenium Client Bindings |
|---|
| DOCS:Best Practice: Use the Latest Version of Selenium Client Bindings |
|---|
|
Use Small, Atomic, Autonomous Tests
| Include Page |
|---|
| DOCS:Best Practices: Use Small, Atomic, Autonomous Tests |
|---|
| DOCS:Best Practices: Use Small, Atomic, Autonomous Tests |
|---|
|
Use Page Objects to Model Repeated Interactions and Elements
| Include Page |
|---|
| DOCS:Best Practice: Use Page Objects to Model Repeated Interactions and Elements |
|---|
| DOCS:Best Practice: Use Page Objects to Model Repeated Interactions and Elements |
|---|
|
Use Breakpoints to Diagnose Flaky Tests
| Include Page |
|---|
| DOCS:Best Practice: Use Breakpoints to Diagnose Flaky Tests |
|---|
| DOCS:Best Practice: Use Breakpoints to Diagnose Flaky Tests |
|---|
|
Use New Accounts for Each Test
| Include Page |
|---|
| DOCS:Best Practice: Use New Accounts For Each Test |
|---|
| DOCS:Best Practice: Use New Accounts For Each Test |
|---|
|
Avoid Leakage of Credentials
| Include Page |
|---|
| DOCS:Best Practice: Avoid Leakage of Credentials |
|---|
| DOCS:Best Practice: Avoid Leakage of Credentials |
|---|
|
Be Aware of the Load on Your Servers
| Include Page |
|---|
| DOCS:Best Practice: Be Aware of the Load on Your Servers |
|---|
| DOCS:Best Practice: Be Aware of the Load on Your Servers |
|---|
|
Imperative v. Declarative Test Scenarios
| Include Page |
|---|
| DOCS:Best Practice: Imperative v. Declarative Testing Scenarios |
|---|
| DOCS:Best Practice: Imperative v. Declarative Testing Scenarios |
|---|
|
Use Maven to Manage Project Dependencies
| Include Page |
|---|
| DOCS:Best Practice: Use Maven to Manage Project Dependencies |
|---|
| DOCS:Best Practice: Use Maven to Manage Project Dependencies |
|---|
|
