43 Salesforce Test Cases: Templates and Examples [2026]

How Do You Use This Salesforce Test Case Checklist?

Use the categories below as a ready checklist: each explains what to test and why, and five include a fully worked test case you can copy and adapt to your own org.

The remaining categories follow the same structure once adapted: a unique ID, a clear precondition, numbered steps, the test data used, and a specific expected result.

A consistent ID naming convention keeps a large test suite traceable as it grows. The convention used in the worked examples below is TC_MODULE_NUMBER, for example TC_UI_001 for the first UI test case, or TC_APEX_003 for the third Apex test case. Use whichever convention your team already uses for other systems; consistency matters more than the specific format chosen.

To get started, use this open-source, free-to-use Salesforce test case template sheet as a living resource to track your Salesforce testing procedure: Salesforce Test Case Template Sheet.

Many of these categories surface most clearly inside a specific business process rather than in isolation: the assignment rules, status automations, and email-to-case logic that Salesforce case management depends on are a good example, since a single case record touches integration, validation rules, and workflow testing all at once.

Salesforce Test Case Categories

The Salesforce test case examples below are grouped by category to help streamline coverage planning, whether the focus is UI testing, accessibility testing, or any of the 43 areas covered.

1. What Does Salesforce UI Testing Verify?

Salesforce UI testing is crucial since it ensures the system is simple to use and that the organization and style of pages, buttons, and links are appropriate and consistent.

During UI testing in Salesforce, testers thoroughly examine the system's pages, buttons, and links to ensure they are functional and properly aligned, and examine the interface's functionality across browsers and devices to ensure it is responsive and performs properly across platforms.

Here are some examples of what to involve in UI testing:

• Examining the alignment and spacing of web elements.
• Testing the operation of buttons and links.
• Examining the data presented in fields and objects.
• Examining the presentation of reports and dashboards.
• Examining the system's behavior in various browsers and devices.
• Testing the system's accessibility for users with disabilities.
• Validating conformity with design standards such as the Salesforce Lightning Design System.
• Checking for conformity with any branding guidelines.

Worked example, TC_UI_001:

A test case like the one above starts as a manual check, but it is also a simple candidate for automation. Once validated by hand, the same three steps can be converted into a Selenium automation script or covered through Playwright testing, since neither the button location nor the assertion changes between runs.

What does change across releases is the underlying Lightning markup, which is where Shadow DOM handling and a Salesforce-specific locator strategy, rather than generic web automation, start to matter.

2. Why Is Data Integrity Testing Important?

Data integrity in Salesforce testing is important because it verifies data accuracy and consistency.

During data integrity testing, testers check validation rules, data import/export functionality, and data behavior across various fields and objects to ensure data is correctly input, stored, and retrieved. Validation rules ensure the data entered meets the system's criteria, while data import/export capability is tested to confirm data can be imported and exported accurately.

Here are some points included in data integrity testing:

• Validation rules must be correctly implemented and enforced.
• Testing data import and export to ensure data is properly structured.
• Ensuring that data is shown accurately in various fields and objects.
• Ensuring that data can be searched and sorted accurately.
• Examining data consistency following the backup and restore process.
• Examining data consistency following the rollback process.
• Checking data consistency following upgrades and releases.
• Examining data consistency across several objects.
• Examining data consistency in production and Sandbox environments.
• Examining data consistency following data migration from external systems and third-party apps.

It is critical to have a comprehensive Salesforce testing plan and to collaborate with a team of professional Salesforce developers and testers to guarantee all components of the system are adequately verified against the required data integrity.

Most data integrity failures that reach production were technically catchable earlier, they just were not caught because the environment used for validation did not resemble production closely enough.

3. What Does Customization Testing Cover?

Customization testing ensures system adaptations such as new fields, custom objects, and custom workflows do not interfere with existing functionality and meet requirements.

During customization testing, testers confirm that custom fields, custom objects, and custom processes are functional and meet requirements, while ensuring alterations do not interfere with current functionality such as data integrity, performance, or security.

• Verifying that custom fields and custom objects are correctly aligned and displayed.
• Testing custom workflows to check they are properly triggered.
• Custom metadata is tested for correctness and coverage.
• Ensuring custom permissions are properly displayed and aligned on the page.
• Custom labels are tested for correctness and coverage.
• Checking the validity and coverage of Lightning components.
• Visualforce pages are tested for correctness and coverage.

It is critical to properly test customizations to ensure they do not introduce new problems into the system and that they fulfill requirements.

4. What Is Salesforce Integration Testing?

Integration testing in Salesforce helps ensure the system can communicate and share data with other systems correctly, such as external databases or other platforms.

Testers validate communication and data exchange between Salesforce and other systems to ensure the connection functions properly, data is transmitted and synchronized correctly, and the integration meets requirements.

• Salesforce and other systems' connections and communication should be tested.
• Test the data flow between Salesforce and other platforms.
• Run data synchronization tests between Salesforce and other platforms.
• Test the integration with third-party applications.
• Run integration tests using external systems.
• Test security during the integration process.
• Test data migration from external systems and third-party apps.
• Test error handling during the integration process.

Worked example, TC_INT_001:

5. What Does Salesforce Security Testing Check?

Security testing ensures the system is secure and meets industry standards, checking user access control, data encryption, and regulatory compliance.

Testers verify that user access control, data encryption, and industry-standard compliance are all working properly and effectively, and that the system can handle and respond to security threats such as hacking attempts, unauthorized access, and data breaches.

• Testing user access control to ensure only authorized users have access to sensitive data.
• Testing data encryption to guarantee data is secure against unauthorized access.
• SOC 2, PCI-DSS, and HIPAA compliance testing.
• Testing the system's ability to handle and respond to unauthorized access.
• Testing the system's capacity to detect and respond to phishing attempts.
• Testing the system's capacity to manage and respond to malware and other dangerous code.
• Evaluating the system's logging and auditing capabilities.
• Testing the system's ability to handle and respond to hacking attempts.

Worked example, TC_SEC_001:

It is essential to extensively evaluate the system's security to ensure it can manage and respond to threats efficiently and fulfills industry standards, helping identify vulnerabilities before they reach production.

6. What Does Performance Testing Measure?

Performance testing assures the system can manage anticipated usage and function well under various loads and conditions.

Testers verify the system can handle various loads, a large number of users, significant data volumes, and complex transactions, to ensure it can meet user needs.

• Evaluating the response time of the system under various loads.
• Checking the system's capacity to manage many users at once.
• Testing the system's capacity to handle massive amounts of data.
• Evaluating the system's handling of complicated transactions.
• Evaluating performance during periods of high usage.
• Testing the system's adaptability to various data types.
• Testing memory and CPU utilization under various loads.
• Testing the scalability of the system.

Performance testing is crucial because it evaluates whether the system can handle anticipated usage and function efficiently under various conditions, helping locate performance bottlenecks before they affect real users.

7. Why Run Cross Browser Testing on Salesforce?

Cross browser testing of Salesforce applications assures the CRM works well and is easy to use across various browsers and mobile devices.

Testers verify the system's functionality works appropriately on mobile devices and that layout and style remain consistent.

A major challenge with cross browser testing of Salesforce applications is building and maintaining the infrastructure to cover every browser and OS combination a customer base actually uses, rather than the two or three a team happens to have installed locally.

• Testing system performance on various browsers, OS, and devices.
• Testing webpage layout and web design on various browsers, OS, and devices.
• Testing the webpage's responsiveness for handling different resolutions, orientations, touch inputs, and network conditions.

8. What Is Load Testing in Salesforce?

Salesforce testing must include load testing to ensure the system can support the anticipated volume of users and transactions and function effectively under pressure.

• Evaluating the system's capacity to manage the anticipated number of active users, transactions, and requests.
• Testing performance, response time, and scalability during heavy loads.
• Evaluating the system's capacity to cope with various network, server, and database configurations under heavy loads.

9. What Does Stress Testing Validate?

Stress testing assures the system can withstand and recover from unexpectedly high loads.

Testers simulate extreme usage situations to assess the system's ability to manage and recover from unforeseen scenarios, such as network outages, while retaining data integrity throughout.

• Testing resilience to unexpected high loads, unforeseen failures, and network outages.
• Testing the system's ability to handle server failure, database failure, and power outages, and capacity to recover.
• Testing the system's capacity to retain data integrity and operation under unforeseen circumstances.
• Testing resilience to security breaches, system failures, and data loss.

10. Why Is Regression Testing Essential?

Regression testing is essential since it guarantees system changes such as updates and releases do not damage existing functionality and the system keeps functioning as intended.

• Rerun previously completed test cases to confirm the system is still functioning properly.
• Evaluate functionality, performance, data integrity, and security after updates and releases.
• Check the system's adherence to industry standards after updates and releases.
• Test resilience to unexpected failures, network outages, and server or database failures after updates.

11. What Is User Acceptance Testing (UAT)?

Salesforce testing must include User Acceptance Testing (UAT) to confirm that the system meets business requirements and is ready for release to end users.

During UAT, testers validate key areas including functionality, usability, performance, security, data accuracy, integrations, and the completeness of supporting documentation such as user guides and manuals.

To ensure UAT reflects real-world usage, testing should be performed in a dedicated UAT environment that closely mirrors production. The UAT environment should contain masked production-like data volumes, fully operational integrations, and clearly defined entry and exit criteria. This enables users to identify data integrity issues, process gaps, and potential release risks before the solution is deployed to production.

• Test functionality, usability, performance, security, and other important parameters.
• Verify user manuals and documentation are correct and complete.
• Check compliance with industry requirements and branding standards.
• Check that the system complies with company requirements.
• Check whether the system is prepared for release to users.

UAT is performed by end users or a UAT team comprised of end users, stakeholders, and business analysts, and is critical to ensuring the system meets requirements before release.

Download This Free Salesforce Testing Checklist to Find Failures Before They Impact Users

Download Free Checklist

12. What Does Disaster Recovery Testing Confirm?

Disaster recovery testing ensures the system can handle and recover from unforeseen events.

Testers simulate disasters such as power outages, network failures, and hardware failures to assess recovery capability, and confirm the disaster recovery plan maintains data integrity and functionality throughout.

• Testing resilience to power breaks, network failure, and hardware failure.
• Evaluating the system's ability to handle natural disasters, man-made disasters, and security breaches.

13. Why Is Accessibility Testing Needed?

Accessibility testing makes sure Salesforce is usable by people with disabilities and complies with ADA and WCAG accessibility standards.

It confirms compliance by validating usability with assistive technologies such as screen readers and keyboard-only navigation.

• Check compliance with WCAG and ADA accessibility requirements.
• Test functionality using assistive technology like screen readers and keyboard-only navigation.
• Confirm the availability of alternative text for visuals and videos.
• Examine forms and inputs to ensure labels are accurate.
• Check that color and contrast conform to accessibility guidelines.
• Confirm the accessibility of error notices and messages.

The process can be improved through automated accessibility testing using tools like axe and WAVE, combined with manual accessibility checks to identify usability issues that automated tools may not detect.

14. What Is Apex Code Testing?

Apex code testing is a technique for checking the functionality of individual pieces of code, such as Apex classes and triggers.

In Salesforce testing, Apex test classes are used for unit testing: collections of methods that execute test procedures examining a specific aspect of the class under test.

The ideal approach for an Apex test class is to test all potential scenarios, including positive and negative cases, with a test method for each method in the class under test, for example verifying a method correctly accepts both valid and invalid input such as null values or wrong data types.

Salesforce's built-in test runner, accessed from the Developer Console, executes Apex code testing and provides full details on tests run, passed, and any failures. Additional tools like the Apex Test Execution page and Apex Test Execution History support managing test methods, viewing results, and analyzing code coverage.

Worked example, TC_APEX_001:

Salesforce also provides additional testing options such as Asynchronous Testing and Testing Web Services, which can be evaluated to determine which fits the organization's Apex code best.

15. What Are SOQL and SOSL in Salesforce Testing?

SOQL and SOSL are Salesforce query languages used to retrieve data; SOSL searches across several objects, while SOQL obtains data from a single object.

SOQL and SOSL testing verifies these queries operate properly and produce desired results, checking query syntax, running them through various filters and conditions, and confirming returned data is correct.

Apex test classes can run SOQL and SOSL searches and confirm the results line up with expectations, and third-party tools like SOQL Tester offer a user-friendly interface for running and inspecting queries.

It is important to test queries under various conditions (different filters, conditions, and data types) to verify they are operating properly and producing the desired results.

16. What Is Sandbox Testing in Salesforce?

Sandbox testing is the practice of testing system modifications in an environment separated from production, letting teams validate changes before deployment.

This ensures the system operates as intended, prevents unexpected impacts on production, and provides a secure environment for experimentation, validation, and user training.

Various types of Salesforce Sandboxes are available, including Full Sandboxes, Partial Copy Sandboxes, and Developer Sandboxes, each designed for different testing needs and data refresh cycles. A Developer Sandbox supports individual development and debugging activities, while a Full Sandbox provides a near-complete replica of the production environment.

It is essential to test all aspects of the system, including data, customizations, workflows, and integrations, in a Sandbox environment that closely matches production. This helps verify that changes are implemented correctly and that the system remains stable and reliable. Security considerations can also be supported through isolation practices similar to concepts used in browser sandboxing, where environments are separated to reduce potential risks.

17. What Is Salesforce Release Testing?

Salesforce release testing checks a new version of the platform before it is made available to end users.

It confirms the new version contains no new issues, does not break existing features, and remains compatible with current customizations and integrations.

Salesforce releases are classified into major, minor, and patch releases. Major releases add new features and introduce significant platform changes, while minor and patch releases focus on smaller enhancements, updates, and bug fixes.

Release testing requires a dedicated testing team and a detailed test strategy, with a test plan listing the test cases to be executed and expected results. The testing scope should cover new features, customizations, integrations, and regression scenarios.

Salesforce test automation helps teams validate releases faster by improving test coverage, consistency, and repeatability. Automated testing tools can further accelerate this process while maintaining accuracy, and it remains critical to test the release in an environment that closely matches production.

Three platform releases a year is exactly where most Salesforce test suites accumulate maintenance debt, including locators that point to renamed fields, validation rules that shift, and Lightning components that re-render differently.

Whether that debt becomes manageable or compounding depends less on which Salesforce test automation tool a team picks and more on whether the framework around it, including data management, CI/CD processes, and locator strategy, is built to support seasonal releases rather than only the current version.

18. What Does Data Migration Testing Ensure?

Data migration testing moves data between systems or Salesforce versions, ensuring it stays correct, consistent, accurate, and accessible in the new system.

• Testing data migration between various systems and between different versions of Salesforce.
• Testing data migration between different contexts, such as development to production.

A clear test plan covering data accuracy, consistency, and accessibility should be in place before performing data migration testing, ideally executed in an environment as close to production as possible.

19. What Does Backup and Restore Testing Verify?

Backup and restore testing verifies Salesforce data can be correctly backed up and restored, and that the procedure is dependable and efficient.

Test cases should simulate scenarios like backing up and restoring specific data sets, and evaluating the restore process with full, incremental, and differential backups. It is also critical that backups are stored securely and can be restored during a disaster, including testing the disaster recovery plan itself.

20. What Does Rollback Testing Determine?

Rollback testing determines the system's capacity to retract changes or undo earlier operations.

It verifies the ability to roll back data, configuration, or code changes, so the system can be restored to its previous state and faults fixed promptly if necessary.

Test cases should evaluate rolling back data changes, configuration changes, or code changes, and test the rollback process across production, development, and staging contexts. This gives the organization confidence the system can be readily rolled back to a stable state if serious difficulties arise.

21. What Is Error Handling Testing?

Error handling testing discovers and corrects system issues by testing scenarios and user inputs across data validity, user permissions, and system integrations.

This ensures the system works properly and users can complete their jobs without issues. Salesforce provides tools like Apex Test Classes and Test Coverage to assist in testing and debugging code, alongside error messages and troubleshooting resources for users.

22. What Does User Permission Testing Verify?

User permission testing verifies how the system enforces user access rights, ensuring users can only access and act on data and objects they are authorized for.

This is accomplished by creating test users with varying permission sets and roles, then simulating scenarios to verify the system correctly enforces access rights at the record, object, and field level.

Salesforce provides the Permission Set and Profile objects for managing and testing user rights, and the runAs() method in Apex code to verify permissions programmatically.

23. What Does Role Hierarchy Testing Ensure?

Role hierarchy testing ensures data security and access control work properly inside the organization.

A role hierarchy groups users by job function or position to establish each user's level of data access, users at the top, such as executives, have full access, while entry-level employees access only a subset.

Salesforce includes the Role object and the Apex UserInfo.getUserRoleId() method for managing and testing role hierarchy, alongside Sharing Rules for sharing records with specific groups or roles,these sharing rules should also be tested to ensure data is shared according to established rules.

24. What Does Customizable Forecasting Testing Verify?

Customizable forecasting testing verifies Salesforce's forecasting feature, which lets users create and manage sales forecasts and can be configured to meet specific needs.

Salesforce provides the Forecasts tab, Forecast Hierarchy, and Forecast Quotas objects for managing and testing this, alongside methodologies like Rolling Forecast and Opportunity Splits.

It is also essential to assess the forecasting feature's integration with reports, dashboards, and other objects, to confirm forecasts are accurately displayed and accessible.

25. What Does Lead Conversion Testing Verify?

Lead conversion testing verifies how the system manages converting leads into accounts, contacts, and opportunities.

This is critical for businesses using Salesforce to manage their sales pipeline, ensuring leads are correctly turned into customers and relevant information is gathered and tracked.

Salesforce includes the lead conversion wizard and lead conversion triggers for managing and testing this process, alongside options like "Convert and Edit" and "Convert and Close" that can be evaluated for fit.

Worked example, TC_LEAD_001:

The same conversion logic above is also where teams first try natural-language test authoring, since the steps map almost verbatim onto a plain-English description, which is what makes automating Salesforce lead generation with KaneAI a practical next step once this test case is validated manually.

26. What Does Data Import and Export Testing Verify?

Data import and export testing verifies data export and import from and into Salesforce, guaranteeing data is correctly transported and relevant data is gathered and tracked.

Salesforce includes the Data Import Wizard, Data Export, and Apex Data Loader for managing this, alongside options like Standard and Custom Objects and Reports and Dashboards.

Testing involves creating test data and recreating scenarios across diverse data kinds, file formats, and data quantities to confirm the system handles export and import correctly.

What Do Test Data Related Test Cases Cover?

Test data-related test cases verify that the data used during Salesforce testing is accurate, secure, and suitable for different testing scenarios.

These cases cover data creation, isolation, rollback, and validation to ensure reliable test execution without impacting production data.

30. What Does Validation Rule Testing Cover?

Testing validation rules verifies the rules used to guarantee data entered into the system is correct and complete before saving a record.

This includes testing for various input values, user activities, and system conditions, and testing the integration of validation rules with reports, dashboards, and other objects.

31. What Does Trigger Testing Verify?

Trigger testing verifies Apex triggers used to automate Salesforce system actions, improving data integrity and consistency.

Triggers are tested by creating test data and simulating scenarios across various input values, user behaviors, and system states, including their integration with other Salesforce features to ensure no unexpected results occur.

32. What Does Workflow Testing Evaluate?

Testing workflows evaluates the actions and rules used to automate Salesforce functions, such as email notifications, field updates, and task assignments.

Workflows are managed and tested using Workflow Rules, Approval Processes, and Flow Builder, verified by creating test data and simulating scenarios across various input values, user behaviors, and system states.

33. What Does Email Service Testing Verify?

Email service testing verifies the services used to send automated emails from Salesforce, such as alerts, notifications, and confirmations.

These services help improve communication with clients and stakeholders, and tools like Email Services, the Apex Email Service, and the Single Email Message support managing and testing this.

34. What Do Test Execution Related Test Cases Validate?

Test execution-related test cases validate running, monitoring, and reporting test outcomes across environments, where automation testing tools improve efficiency, accuracy, and coverage.

• Test Automation: Test the automation of test cases using modern solutions such as TestMu AI Platform to reduce testing effort, improve execution speed, and align with current test automation trends.
• Test Management: Validate the ability to add, edit, organize, and remove test cases efficiently within a test management environment.
• Test Case Execution: Verify the execution process, monitor test outcomes, and ensure automated test workflows run successfully.
• Test Reporting: Evaluate the ability to generate reports on test coverage, execution results, failures, and overall testing progress.
• Test Metrics: Assess the ability to track key metrics such as execution time, pass/fail rates, and test coverage.
• Testing Environments: Validate whether testing can be performed across development, staging, and production-like environments.
• Test Deployment: Verify that system deployments function correctly and maintain stability after release.

What Are Custom Test Cases in Salesforce?

Custom test cases validate Salesforce-specific configurations, components, and business requirements to ensure custom features, objects, and settings function correctly and support user needs.

42. What Does Lightning Component Testing Verify?

Testing Lightning components verifies the components used to create custom user interfaces and interactions in Salesforce.

These components can be quickly incorporated into the platform to build unique pages, forms, and other UI elements.

Verifying Lightning components requires generating test data and simulating scenarios, including:

• Testing various input values, user behaviors, and system conditions to confirm components function properly without unexpected outcomes.
• Testing integration with other Salesforce features like reports, dashboards, and other objects.
• Considering test data management, isolation, and rollback to ensure test cases run with accurate, pertinent data and trustworthy results.

Salesforce offers tools including the Lightning App Builder, the Lightning Component Library, and the Lightning Component Test Framework to manage and test Lightning components.

43. What Does Visualforce Page Testing Verify?

Testing Visualforce pages verifies pages used to build unique user interfaces and interactions in the Salesforce system.

The framework lets developers design custom pages and other system-integrable components.

• Generate test data and simulate situations to verify pages function properly.
• Test various input values, user behaviors, and system conditions.
• Test integration of Visualforce pages with reports, dashboards, and other objects to confirm nothing unexpected occurs.

Tools including the Visualforce Developer Console, Apex Code, and Visualforce Page Test Framework support managing and testing Visualforce pages.

To get started, use this open and free Salesforce test case template sheet as a reference to stay current on the testing process: Salesforce Test Case Template Sheet.

Manage Your Salesforce Testing with TestMu AI

Running 43 categories of test cases by hand, every release, across every browser a customer base uses, is not a staffing problem most teams can solve by hiring more testers; it is a coverage-versus-time tradeoff that only changes with the right execution layer underneath it.

TestMu AI (Formerly LambdaTest) is a Full Stack Agentic AI Quality Engineering platform built for exactly that tradeoff: AI agents plan, author, execute, and analyze test coverage across web, mobile, and enterprise applications like Salesforce, at scale, across real devices, real browsers, and custom environments. Applied to the categories above, that includes:

• Debugging Salesforce tests with command logs, network logs, and video recordings.
• Executing Salesforce tests 70% faster with HyperExecute, the end-to-end test orchestration cloud from TestMu AI.
• Executing Salesforce tests in parallel across multiple configurations to cut execution time significantly.
• Easy integration with CI/CD pipelines.
• Support for all major browser testing frameworks beyond Salesforce, including Selenium, Playwright, and Cypress.

Wrapping Up

Salesforce testing is an essential step during the development and deployment of Salesforce applications. It helps ensure an application meets business requirements, is free from bugs, and functions as expected, giving quality assurance that improves the likelihood of fast user adoption.

This guide covers all major test case categories required during Salesforce testing, with worked examples for the categories teams ask about most. Test case templates matter because they help the system work as intended and remain maintainable over long periods, improving the overall user experience and making it easier for testers and developers to manage the platform.