Instructions

Why automate?
In today’s increasingly digital world,
businesses need to keep up to speed with
rapid changes in the market and shifting
customer demand.
This requires Product teams to deliver new
features and customizations faster than
ever before, and it puts pressure on Quality
Assurance, who must ensure the functionality
and security of these releases.
Salesforce is a programming platform with its
own programming language (APEX) and own
database system, meaning that enterprises
can build totally customized applications, with
unique screens and features, on top of this
technological foundation.
On top of that, Salesforce regularly update
their platform to enhance user experience
and/or to fix underlying issues. Each release
can include big improvements to the cloud-
based interface.
Testing Salesforce
Releases: Everything You
Need to Know
With the limited time available for
testing Seasonal Releases, how can you
ensure new features aren’t breaking
customizations and configurations?
Get this whitepaper for insight into
rethinking how testing is done in your
next seasonal release.
Get the whitepaper
Unfortunately, these changes can impact user
customizations and even standard uses of the
platform. For QA teams, this means a lot of
maintenance.
Organizations who have taken a manual
approach to testing know that it becomes an
ever-increasing bottleneck, causing slower
time to market, resource scarcity, and risk to
business continuity.
Many companies will turn to a manual, “risk-
based approach” to testing in which testers
focus on the most important features - and
ignore the rest. At a time when companies
should be moving towards continuous, 24/7
testing, this fragmented, manual approach
leaves considerable gaps in test coverage and
quality.
Salesforce Automation Guide 4