Salesforce testing

Automated end-to-end testing for
the Salesforce multi-cloud

updates icon
Stay ahead of Salesforce updates
Quickly catch regressions when there’s an update to Classic or Lightning, or any AppExchange plug-ins — even during preview periods and in sandboxes.
all encompassing icon
Test the whole of Salesforce
Aura & Apex components
ISV & OEM plug-ins
Visualforce components
Chatter components
Process Builder flows
Workflow rules
Einstein AI
Marketing Cloud
Service cloud
...and everything else
lock icon
Validate compliance & security
Check that data security and privacy rules are maintained after each release, on both Salesforce and in-house systems, and during transfer.

About Salesforce regression testing

Automated regression testing for Salesforce-powered and -integrated apps is a safeguard against the unpredictable and intertwined systems your business relies on. A routine deployment could be the butterfly wings that causes a hurricane in your sales pipeline, or exposes you to data security risks.

But testing for those overlooked API dependencies or misaligned object relationships isn’t just routine black-box testing. Salesforce has its own SSO implementation, various license restrictions, a custom implementation of the shadow DOM, and both Classic and Lightning versions — most people just cross their fingers and hope for the best when testing their Salesforce-based app.

But then we’re not most people.

How it's done

Regression testing every Salesforce integration

Automated QA for apps that move data in and out of your Salesforce, run custom Apex components, or sell a complete solution on AppExchange.

Test on your environments, or Salesforce’s

Our cloud infrastructure can run against any of your environments, as well as Salesforce’s sandboxes and scratch environments. We’ll help you decide the best mix based on your data and system configurations.

Test data set up and teardown

Using an API, the Salesforce Data Loader, an Apex utility class, or on-demand migrations from Production to a sandbox.
Salesforce data loader
qa wolf concurrency selection

Parallelized test runs

Containerized tests use their own API tokens with individual rate limits.

Pre-update checks

Avoid regressions by testing during preview periods on sandbox and scratch environments.
code snippet for salesforce environments
list of bugs

Bugs bagged and sorted

Bug reports come back in minutes, already tagged as affecting production or pre-release preview versions of Salesforce.

Bugs bagged and sorted

list of bugs
Bug reports come back in minutes, already tagged as affecting production or pre-release preview versions of Salesforce.

Salesforce Testing 360

If Salesforce is integrated into your application, it’s pretty much guaranteed to be connected to a critical business process that cannot break down. You need comprehensive regression tests throughout the flow of data, running every day and every deploy, to catch regressions before they become revenue losses.

Data integrity and visibility

Data syncing and transformation

Make sure your cloud stays in sync with your Salesforce Clouds, reports are accurate, and validation rules are applied.
webform connecting to salesforce
salesforce export modal

Importing and exporting records

Validate data in dozens of file formats, including Excel and PDF.

User permissions and security

salesforce user permissions
Make sure users see and do only what they’re supposed to — no more, no less — at the field level or record level

UI functional testing

Classic to Lightning migrations

dashboard comparison between salesforce classic and lightning
Test that Classic pages and components continue working as you update to Lightning.

Language and framework interoperability

Validate that Lightning Web Components work with legacy Aura components work with Apex triggers, controllers, and extensions — and vice versa.
salesforce custom objects

Custom apps, objects, fields

Test basic functionality, design standards,  events and triggers, data flows, security, and security requirements, and compliance.

Cross-browser & responsive design

Visual and functional testing across various browsers, OSes, and breakpoints.
logos for chrome, firefox, safari

Workflows and business rules

Database loads

Use parallel test runs to simulate heavy loads on database operations, either through the UI or a direct API call.
salesforce triggers

Triggers and automations

Test event-triggered jobs, batch jobs, and time-based jobs.

Notification delivery

Make sure users receive timely email, SMS, and in-app messages.
salesforce dashboard

Calculations and transformations

Carry the one across Salesforce Clouds, data exports, and charts, and tables.

Integrations and API testing

API and schema validation

Validate that API calls return data, that the API is performant, and that the data is structured properly.

AppExchange apps and plug-ins

Run a full suite of tests from authentication configurations to security checks.


Yes we can. And integrations between the clouds and your application. Your Salesforce admin will probably need to configure permissions and other settings, just like a DevOps person would configure your testing environments — but it’s straightforward and we’ll show you how to do it securely.

Absolutely! We’ll create a unique test per experience, which lets us run them in parallel and react faster when a test fails.

We build our tests to create (and destroy) isolated test data, and we’ve found that sandboxes are frequently as effective as testing in production environments. That said, data integrity is one of the most complex aspects of testing Salesforce-integrated applications and as a blackbox service, we don’t get into your codebase. Which is why we over-communicate to make sure that the test data we’re using is appropriate for the test case in question.

Typically a test is configured to launch with the permissions it needs. If the test is to validate a change in permissions, the test will use the interface just as a real user (i.e. a Salesforce admin) would. If necessary, we can also use Salesforce APIs.

Yes. We can test their actual UX, their integration points with your other systems, even the installation flow.

While their updates can break automated tests (just as any update can), mitigating the impact is simple enough. First, we design our tests to be “atomic,” that is the test cases are narrowly-defined, so if something breaks it doesn’t have reverberating impacts. Second, Salesforce is generous enough to provide their updates in preview environments several weeks ahead of the public release. During this time, we monitor the changes and make any updates, preventing any gaps in coverage on your production systems.

We use Microsoft Playwright for test automation, and a Kubernetes and Docker infrastructure to run them in parallel.

Pass/fail results will be shown in the QA Wolf platform, as well as your CI/CD tools. Bugs that have been validated by one of our QA engineers will be captured in Slack (or other chat app) and your issue tracker.

Add Salesforce testing to your QA process

Keep reading