Transcripted Summary
As a Salesforce test engineer, understanding common User Interface (UI) components is vital for executing effective test scenarios. Every Salesforce application consists of standardized layout elements—including input fields, navigation tabs, picklists, buttons, search bars, and modal dialogs. Knowing how these components behave under both valid and invalid testing conditions ensures thorough quality coverage.
# Overview of Essential Salesforce UI Components
| UI Component | Location / Description | Functional Purpose & Testing Consideration |
|---|---|---|
| Navigation Tabs | Top header bar (e.g., Home, Leads, Accounts, Opportunities). | Allows users to switch between standard and custom object views. |
| Global Search Box | Top header bar. | Queries and displays matching records across the entire org based on search keywords. |
| List Views & Filters | Object landing pages. | Filters records (e.g., Recently Viewed, All Leads) and supports pinning default views. |
| Picklists | Record entry forms. | Restricts user input to predefined dropdown choices (e.g., Lead Status). |
| Modal Dialogs / Popups | Action triggers (e.g., Delete). | Displays confirmation dialogs before executing critical record actions. |
# Field Validation and Asterisks
When creating or editing a record—such as a Lead—fields are categorized as mandatory or optional. Required fields are clearly identified by a red asterisk (*). From a QA standpoint, submitting a form without filling in mandatory fields (like Name or Company) immediately triggers UI-level validation error messages.
Different field types impose specific input constraints. Text fields accept alphanumeric characters, whereas picklist fields restrict entries to specific drop-down values. Selecting invalid or unassigned options (such as selecting "None" on a required picklist) generates validation warnings to preserve data integrity.
# Button Actions: Save vs. Save & New
Understanding the operational differences between standard buttons is critical when designing UI test cases.
| Action Button | Expected Behavior & Redirection |
|---|---|
| Save | Validates form data, saves the record, and redirects the user directly to the new Record Detail page. |
| Save & New | Validates and saves the current record, then immediately reopens a fresh creation modal to enter another record quickly. |
# Record Actions and Lifecycle Behavior
Other standard record actions carry specific business logic and UI responses. For example, clicking Convert on a Lead record executes a multi-object lifecycle process that automatically creates linked Account, Contact, and Opportunity records. Conversely, clicking Delete opens a confirmation modal dialogue box to confirm record removal and prevent accidental data loss.
Mastering these common UI components enables QA engineers to write precise test steps and validate front-end system behavior efficiently.
