Testing Salesforce Data Before and After Migration

Correct and accurate data is the most crucial part of an effective Salesforce application. The cost of mishandling the migration of data is high. But the business risk associated with incorrect data like lost revenue and lost opportunities can be enormous. In Salesforce CRM, organizations often face large and complex data migrations. Testing is a key phase in the migration process that uncovers issues before they become a costly headache. To mitigate the risks such as data corruption, missing data, loss of data, and application performance issues involved in data migration, it is important to use a thorough and effective testing strategy.

The Test startegy should encompasses testing by functional area before and after migartion.The floowing lists show what can be examined at both stages of the process.

LIst of Functional Testing Areas to consider prior to data Migration:  
  • Make sure  that all the objects, custom fields, and custom apps are setup correctly before the data migration
  • Validate the organization-wide defaults(OWD) and profiles are setup correctly in the target system
  • Validate that all workflow assessments, approval rules and email templates are migrated
  • Validate that all the page layouts and mapping of page layouts to profiles are setup properly for all the record types
  • Validate that SSO logins are working correctly
  • Validate that all tabs are displayed correctly
  •  
 List of Functional Testing Areas to consider after data Migration:  
  • First test on a small sample of data to check whether the data mapping is implemented correctly or not
  • Validate that all the users are associated with the correct profile
  • Validate that relationships between accounts, contacts, and opportunities have been set up correctly
  • Create a new record to check for required fields, read-only fields, and any validation rules on a particular field 
  • Use sample data to test the approval processes.
  • Validate that workflow scenarios are being triggered and email notifications are being sent via workflow.
  • Validate that search is returning correct records.
  • Check for duplicate data (i.e., duplicate contacts, accounts, and opportunities).
  • Test the records of different objects by logging into Salesforce as different users. Compare these same records manually with the legacy system.
  • Perform basic SOL queries in the developer console to retrieve information like total number of account in a record type, number of accounts with multiple contacts, etc.
  • Validate that site pages are displaying properly.
  • Validate that naming conventions remain the same in the target system.
  • Create custom reports to retrieve the data in target systems and compare with the legacy system.
  • Test for broken attachments and links
  • Validate on records that CreatedBy, CreatedDate, LastModifiedByID, and LastModifiedDate are the same as they are in the legacy system.
  • Monitor the load time carefully and raise issues to avoid bottlenecks.
  • Check that the migrated dashboard and reports are running and displaying the correct records.

  •  

Comments

Post a Comment

Popular posts from this blog

How to calculate maximum number of concurrent users using littile law formula

When load testing an application, the first set of tests should focus on measuring the maximum throughput. This is especially true of multi-user, interactive applications like web applications. The maximum throughput is best measured by running a few emulated users with zero think time. This means that each emulated user sends a request, receives a response and immediately loops back to send the next request. Although this is artificial, it is the best way to quickly determine the maximum performance of the server infrastructure. Littile Law: Once you have that throughput (say X), we can use  Little’s Law  to estimate the number of real simultaneous users that the application can support. In simple terms, Little’s Law states that : N = X  / λ where N is the number of concurrent users,  λ is the average arrival rate and X is the throughput. Note that the arrival rate is the inverse of the inter-arrival time i.e. the time between requests. To under...
Read more

How to develop a security test strategy

What do you need to write a security test plan? The folowing documents comprise the list of what I would expect as inputs to the creation of the individual security test plans. This is a good point to go and review your overall security delivery plan. Does it include these documents as deliverables? Does the supplier have any of these as standard off-the-shelf products? : System security requirements System threat model System risk model Secure coding standards Technical threat modelling Infrastructure secure configuration guides Security defect metrics What is in a security test plan? The security test strategy should as a minimum specify the following points as the core content for each of the security test plans: What are the inputs to the test plan? When in the process does this test occur? Who specifies the test plan contents? Who performs the test? How many instances of the test are expected? What are the required outputs of the test? What are the success...
Read more

Singleton Design Pattern using Page Factory

Image
n this tutorial, We will learn about the  Framework Design Pattern using singleton class  in Selenium. In the Previous tutorial we have seen, How can we run the Test using Page Factory. Now question is, Will we repeat the Browser invoke and Logger code again and again in each and every Test. No, To resolve this issue we will use the Singleton Pattern. We will design the Single  Test Base  class.  First, Let's see what is  Singleton Pattern .  With the Singleton design pattern you can: Ensure that only one instance of a class is created Provide a global point of access to the object In  TestBase  class, we will Design the Singleton Pattern, We will write the command code here and all Test Classes will inherit this  TestBase  class.  n previous Example, we have seen we were invoking  WebDriver   instance  in each @Test. Here, We will Implement the WebDriver initializat...
Read more