The State of Salesforce Testing: Insights, Challenges and Best Practices

Share this article...

Copado conducted a survey of companies using Salesforce to uncover their existing software testing practices. This is the first survey of its kind and I was intrigued to learn more about current practices, as well as ways to improve. 

We all know that testing is critical to success, but we also know that when pressure hits and deadlines loom, something’s got to give. That thing is often in-depth, quality testing. In this post, I’ll explore some of the insights and key findings from the survey. You can also access the full report here, which I highly recommend reading!

”Ownbackup”

Key Findings

Salesforce is the ultimate low-code platform, empowering businesses to ramp up and develop at rapid speed using “clicks not code”. Add to this the ability to install apps from the AppExchange, or integrate using tools like MuleSoft Composer, and you’ve got an all-singing, all-dancing CRM tool. Digital transformation has never been easier – in theory… 

The issue remains that all development, whether code or declarative, requires testing. Testing takes time and there is also a mistaken belief that it’s less important to test changes that don’t involve code.

As a Salesforce Administrator originally from a non-technical background, I’d argue that testing any changes I make is incredibly important, as I may lack the technical awareness to foresee issues. As an Admin, I’m also wielding incredibly powerful tools that look and feel declarative, but are actually code underneath – take Flow for example. 

So, we’re building incredible things on Salesforce, but are we testing them the right way, if at all? And what happens when we don’t test properly… Here are some of the key findings from the Copado survey, which make for very interesting reading:

Lack of Testing is the #1 Risk to Digital Transformation

Based on these key findings, it’s no surprise that 92% of businesses experience production issues. Worryingly, finding bugs or defects after changes have gone live can cost 640X more to repair. Let’s not forget that issues in production have more than just a monetary cost; they will also cause issues with user adoption at all levels, compromising users’ trust in your Salesforce platform.

How are Companies Testing Salesforce Today?

Our reliance on manual testing can increase our inability to complete testing in time. With 64% of teams using this method and 84% of organizations partially relying on manual testing, this is certainly a cause for concern.

The Benefits of Automated Testing

It’s clear from the results of the survey that automated testing can support businesses and reduce technical issues. Automated testing has multiple benefits:

  • Teams using automated testing experienced less than half as many production failures per year as a result of releases (a median of 3 per year instead of 7).
  • Teams using automated testing release 50% more frequently than those relying on manual testing (34 times per year on average, compared to 22 times per year).
  • Teams using automated testing were 50% more likely to complete all of their test plans for each release (67% of teams using automated testing reported completing all their tests for each release vs. only 45% of teams relying on manual testing).

Summary

The 2022 State of Salesforce Testing report from Copado makes for very interesting and informative reading – be sure to check out the full report here. It’s clear that with great power comes great responsibility; Salesforce provides us with the tools, but we must ensure that we are testing properly, thoroughly, and frequently. 

Not only should we explore new ways and tools to automate our testing, we must also educate ourselves and our businesses; testing is a critical part of software development and cannot be sacrificed due to looming deadlines or a lack of resources or time. 

For more information, check out our post “Salesforce Testing – Everything You Need to Know”.

”Salesforce”

Add Comment