Friday, 09 December 2016 02:37

Data Testing Automation for Salesforce using ETL Validator Featured

Written by
Rate this item
(0 votes)
salesforce data testing salesforce data testing

Over the last few years, the Salesforce platform has become an incredible force in the market for various reasons. Of course, the most obvious use case is for the CRM capabilities. In addition, many organizations have started using the power of the force platform to build and deploy custom applications in the cloud at an incredibly fast pace.

 

While this journey is truly exciting, there will always be a burning underlying need to be able to test the data and ensure that it is always as expected. In this blog, I just thought of highlighting a few use cases and how ETL Validator can help you in addressing those.

Use Case 1: Comparing the data between a Salesforce Org and an OnPremise database.

Consider a simple order capture application that has been moved from an OnPremise to Salesforce. Also assume that the application has few basic objects; Account, Products, Order and Order Line Item tables. Now, after you move the data, few questions emerge:

  1. Did I get ALL the accounts from On Premise application to the Salesforce app?
  2. What is the best way for me to compare the counts?
  3. Are all the records between Salesforce and On Premise system matching from a data integration perspective?
  4. Is referential integrity between accounts, orders and order line items properly maintained in Salesforce?

 

These are simple questions but are extremely important to have the confidence on the data migration process to the Salesforce platform. Using ETL Validator, you can easily create connections between Salesforce and your On Premise Database and execute the above tests in no time.

 

Use Case 2:  Baselining the Product Catalog

Lets’s say there are 1000 products in the catalog and it is important  to ensure that that the metadata of this product catalog does not get accidentally modified. How would you do that?

 

In ETL Validator, you can baseline a table and then run tests on an ongoing basis to ensure that the data accidentally does not get modified. If it does, then the platform can send out notifications with the records that do not have data as expected.

 

Use Case 3: Metadata Comparison

Over a period of time, it is important to understand the changes to profiles, roles, access privileges etc in the Salesforce platform so that only the expected changes are going in with each internal release and nothing else is slipping through the cracks.



Using ETL Validator, you can take a baseline of the object metadata and then compare the same over time. If there are any differences, similar to the above use case, ETL Validator can send out notifications and alert administrators of unexpected changes.

 

To learn how to get started with Salesforce,  you can check this out the link below:

http://datagaps.freshdesk.com/support/solutions/articles/1000241490-connecting-to-salesforce

Read 834 times Last modified on Wednesday, 11 January 2017 17:07