image

Agile Testing/DevOps

How the Tricentis 12.2 Release Streamlines Salesforce Testing and Simplifies the Transition to Salesforce Lightning

The Tricentis Platform 12.2 release announced last week includes a new, AI-assisted Salesforce engine for Tricentis Tosca that significantly streamlines Salesforce testing and reduces test maintenance during a Salesforce upgrade. The Tricentis Tosca Salesforce engine enables enterprises to create reusable test modules that work across both Salesforce Classic and Lightning versions. By scanning the entire Salesforce instance and instantly identifying controls, the engine enables testers to save hundreds of test case creation hours when updating Salesforce or transitioning to Salesforce Lightning.

To see the Tricentis Tosca Salesforce Engine in action, register for the May 16 webinar, “What’s New In Tricentis Platform 12.2.” During the webinar, we’ll demonstrate the AI-assisted Salesforce engine, as well as other platform enhancements including major UX improvements for API Testing, agile testing improvements in regulated industries, a reinvented integration with Tricentis Flood and more. 

Register for the Webinar

To understand why this new release is so critical for enterprises leveraging Salesforce changes and its integrated systems, let’s look at the business context along with the key challenges that arise when testing a Salesforce.com instance.  

Salesforce Lightning Readiness Requires Testing

Most enterprises are using Salesforce Classic and need to transition to Salesforce Lightning in order to use new innovations on the platform. While we don’t know for sure when the mandate to use the Lightning version will take effect, we do know that it will likely be coming soon.  

When talking with our customers, we hear most enterprises have or are currently transitioning to Salesforce Lightning. But a few key challenges have kept some enterprises from making the switch:

  • Costs associated with the transition are high (including migration and Lightning readiness testing) 
  • Automated tests built on Salesforce Classic typically can’t be reused for Lightning and have high re-structuring and maintenance costs associated 

Salesforce Testing Challenges  

Once the migration to Salesforce Lightning is complete, technical challenges will inevitably follow suit. Salesforce controls are dynamic, and a substantial amount of time is spent on identifying stable locators. This technical problem was highlighted by many people we talked with at the largest Salesforce World Tour in APAC. Here are some of the most common complaints we heard:

  • “When I design the test cases with the objects identified, they execute unreliably in Salesforce.Elements do not get consistently found in the UI.” 
  • “All pages have dynamic parameters (such as ID and name), and objects are not recognized consistently so test cases fail.” 

To combat these challenges, technical, automated test cases and locators will have to be re-coded when the transition to Lightning occurs. Even after the Lightning test cases are recreated, additional test script maintenance surfaces with each internal release — at least three times a year, in conjunction with the major releases Salesforce rolls out each year.

How Tricentis Eliminates Salesforce Testing Challenges 

With Tosca’s new Salesforce engine, we solve both of these challenges by enabling enterprises to scan the entire Salesforce instance to create reusable test modules that work across both Salesforce Classic and Lightning versions. This eliminates the need to recreate test cases when transitioning to Lightning and significantly minimizes test case maintenance.  

With our new Salesforce engine, we solve both the business and technical challenges through ability to scan your entire instance of Salesforce to create reusable test modules across both Salesforce Classic and Lightning versions.  

The Salesforce scanner can instantly identify controls in a way that is interface independent, saving teams hundreds of test case creation hours. 

This engine also solves test maintenance issues through Tosca’s model-based framework. For instance, if you add a new Salesforce field, a simple re-scan will keep your test cases up to date without needed to re-identify dynamic fields.  

More Resources for Salesforce Test Automation