Report Strategies in Salesforce Testing
The article is based on standard reports strategies being used in Salesforce. By using the standard reports, the below functionalities are going to be tested.
1. Validating the Converted Leads
2. Verifying the Bounced emails
3. Validating the Case Age through standard report
Validating Converted Leads:
Every business lifecycle in Salesforce starts with the lead. Leads are the protentional customers who show the interest to buy our products. Once the leads are qualified to buy the product, they are converted into Account, Contact, and Opportunity. The qualified leads will not be visible in Lead object.
The ‘Converted lead’ can be validated through two ways:
1.Validation of the converted lead through Reports
2.Validation of the converted lead through Queries
Validating the converted leads through reports helps analyze the number of leads converted in a period of time or analyze all the leads that are converted.
Validation of the converted leads through Report:
The best way to identify the converted lead is using reports. Tester should navigate to the Reports tab[Symbol]Click ‘New Report’[Symbol] Select ‘Lead with Converted lead information’ report type[Symbol] Click the create button. This action takes us to the ‘New Report page’. By entering the below condition, we can get the Leads converted today.
The condition is Date field = ‘Converted date’ and Range = ‘Today’. Finally Click ‘Run Report’ to get the final output.
Validation of Converted Lead by using queries:
By using queries, we can also find the converted leads. To execute the query, we should navigate to the ‘developer console’ from the user menu in Salesforce organization. In developer console[Symbol] Click the Query Editor and type the query to get the lead which is converted by today.
Verification of bounced emails:
Bounced email is the email that cannot be delivered to the receiver due to some reasons. It returns the email to the sender. It has two kinds of bounced emails such as hard bounce and soft bounce. Hard bounce occurs because of the invalid domain names and the invalid user names and this email is permanently bounced back to the sender. Soft bounce occurs if the Mail box full, server is down, deleted email address, etc. This email is temporarily bounced back to the sender.
If a Case is raised by consumer, then an email notification will be sent to that consumer. At times, the email might get bounced. This is explained through Salesforce.
Case is created by selecting the contact through lookup. The contact in this example has Invalid email address (Invalid username and domain). I have enabled the checkbox to ‘send notification email to contact’. This email will get bounced. It can be validated in the report with the bounced date and bounced reason.
Tester should navigate to the ‘Reports’ tab[Symbol]Click ‘New Report’[Symbol] Select ‘Contact and Account’ report type[Symbol] Click create button. This action takes us to the ‘New Report’ page. The criteria to get the bounced email is Date field = ‘Email bounced date’ and Range should be selected. By using this, we can get the bounced emails report Finally, click ‘Run Report’ to get the final output.
The above contact has a deleted or non-existing email account. So, it will get bounced. It can be validated through report. This same case is used for ‘Blocked emails’ example also.
The mentioned contact has invalid address (Invalid username with correct domain). It will get bounced and can be verified through report.
In this case, the bounced reason should vary from other reasons.
If the receiver’s mailbox is full (i.e.), all new emails will bounce. Also, If the server gets overloaded, then also the emails will bounce.
This bounced email can be also reviewed in the contact edit page. If any email gets bounced, the email shows the confirmation notification, but this will take more time to validate for every contact’s email. The best way to verify the bounced mails is reports.
Validation of Case Age:
Case Lifecycle is used to track the duration of the case based on the status of case. If case created is in ‘New’ status. To track the age of the cases, the tester should navigate to the reports tab[Symbol] Click ‘New Report’[Symbol] Select ‘Case Life cycle’ from the customer support reports[Symbol] Click create button. This action takes to the new report page.
For Example, I have taken a case number (00001081).
The case is created with the status new. Here, the case age is calculated as follows,
Case Age = Current Time – Case Creation Date/Time
Case is created on 2/9/2017 and today’s date is 2/16/2017. Case age is 7 days. Units can be defined in days, hours and minutes.
The same case is moved from the status ‘new’ to ‘working’. Modification time is reviewed in minutes. The case with the new status shows the time as 7 days and 093 minutes. Once the status is moved, age should change as 7days and 097 minutes.
Here the record count plays a great role. If the case status is ‘new’, the record count will be as 1. When the status gets changed from the new to ‘working’, the record count will be as 2 and so on. So, this record count is added based on the status of the case.
The same case is moved from the status ‘working’ to ‘escalated’; here, again the modification time is reviewed in minutes. The case with the working status shows the time as 7 days and 097 minutes. Once the status is moved, age should change as 7days and 101 minutes. Here, the record count is 3 because the case is moved into the 3rd status.
The same case is moved from the status ‘escalated’ to ‘closed’; here, again the modification time is reviewed in minutes. The case with the escalated status shows the time as 7 days and 147 minutes. Once the status is moved, the age should change as 7days and 101 minutes. Here, the record count is 4 because the case is moved into the 4rd status.