SOAP UI is powerful tool and in this post we will see how it can be used to perform load testing of Salesforce API.

Step 1 : Download PartnerWSDL from your Salesforce instance and create SOAP UI Project.

Step 2 : Create a Test Suite in SOAP UI

Step 3 : Create a Groovy script to generate random Account Name

def generator = { String alphabet, int n ->
  new Random().with {
    (1..n).collect { alphabet[ nextInt( alphabet.length() ) ] }.join()
  }
}

def accName = generator( (('A'..'Z')+('0'..'9')).join(), 9 )
testRunner.testCase.getTestStepByName("AccParameter"). setPropertyValue("AccountName",accName)

def accNumber = testRunner.testCase. getPropertyValue("AccountNumber")

Step 4 : Create a Login request in SOAP UI using Partner WSDL, sample request looks like

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:partner.soap.sforce.com">
   <soapenv:Header>
      <urn:CallOptions>
         <urn:client>?</urn:client> 
      </urn:CallOptions>
      <urn:LoginScopeHeader> 
         <!--Optional:--> 
      </urn:LoginScopeHeader>
   </soapenv:Header>
   <soapenv:Body>
      <urn:login>
         <urn:username>SFUsername</urn:username>
         <urn:password>SFPassword</urn:password>
      </urn:login>
   </soapenv:Body>
</soapenv:Envelope>

Step 5 : Create property step to create two parameter as shown in below

Step 6 : Create Step with property transfer. In this step, we would read Salesforce session Id returned by Login API and pass it to create Account API. To compute X-Path, we can use xmlGrid website.

XPath to read Session of Salesforce

/*:Envelope/*:Body/*:loginResponse/*:result/*:sessionId

X-Path to pass Session Id in Create request

/*:Envelope/*:Header/*:SessionHeader/*:sessionId

Step 7 : In this step we would insert Account using SessionId transferred from previous parameter transfer step

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:partner.soap.sforce.com" xmlns:xsi="xsi">
   <soapenv:Header>
      <urn:PackageVersionHeader/>
      <urn:LocaleOptions/>
     <urn:MruHeader>
      </urn:MruHeader>
      <urn:SessionHeader>
         <urn:sessionId>Salesforce Session Id</urn:sessionId>
      </urn:SessionHeader>
   </soapenv:Header>
   <soapenv:Body>
      <urn:create>
      	<urn:sObjects xsi:type="urn1:Account" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      		<Name>${AccParameter#AccountName}</Name>
      		<AccountNumber>${AccParameter#AccountNumber}</AccountNumber>
      		<TextField__c>InsertedViaSoapUI</TextField__c>
      	</urn:sObjects>
      </urn:create>
   </soapenv:Body>
</soapenv:Envelope>

In this step, you might get this error “Destination URL not reset. The URL returned from login must be set in the SforceService“. To resolve this, change URL of request in SOAP UI address bar. Shown in 30 Min Video below

Step 8 : Final step is to create a Groovy script to auto increment Account Number

def accNumber = testRunner.testCase.getTestStepByName("AccParameter"). getPropertyValue("AccountNumber").toInteger() 
accNumber = accNumber + 1 

testRunner.testCase.getTestStepByName("AccParameter"). setPropertyValue("AccountNumber", accNumber.toString()) 
log.info(accNumber)

Note : Everything we are discussing here is completely covered as part of Live coding in Apex Salesforce Saturday organized by Amit. Would like to thank Mohith for his support and answers during the demo. It also shows How SalesforceDX can be used daily by developers to perform development.

Jasmine and Mocha support is provided as a part of Lightning Test Service (LTS) by Salesforce. Jasmine and Mocha, both are well known and industry wide solution accepted in Javascript world. of course, Salesforce don’t want to stay behind in terms of its offering to developers thats why we have new baby in town – Lightning Test Service (LTS).

You can install Lightning Test Service (LTS) in your org as a part of unamanged package from here. You can also install Lightning Test Service in SFDX using command

sfdx force:lightning:test:install

Once Jasmine is installed, you can navigate in your browser to open Jasmine test runner page using URL https://<YourDomain>.lightning.force.com/c/jasmineTests.app

SFDX Command to open Jasmine Test runner in Salesforce

sfdx force:org:open -p /c/jasmineTests.app

Let’s consider below Lightning component to be used by Lightning Test Service (LTS) 

This Lightning Component uses lightning:datatable component and populates it on basis of input provided.

Now we need to create a Javascript file containing Jasmine test method and upload it as a static resource.

Once, static resource is uploaded in Salesforce, we need to add reference of this static resource in JasmineTests.app . In our case, static resource name is JasmineTestDatatable.  This Test runner application comes as part of Lightning Test Service. Same way, MochaTest runner app also comes as part of LTS.

It is time to open Jasmine Test runner using URL https://<YourDomain>.lightning.force.com/c/jasmineTests.app. We would be able to see below output

Youtube Video of Lightning Test Service (LTS)

Majorly, Jasmine is made up of three functions

1. describe
2. it
3. assertions (expect)

Like standard frameworks, it also has setup method and tear down methods

• beforeEach() – Setup Method
• afterEach() – Teardown Method

For the sake of simplicity of post, I would not discuss much in detail. However, you can navigate to official Jasmine guide for deep dive.

Download Jasmine

You can download latest version of Jasmine from here. Once downloaded, you can extract and save lib folder in your project.

Simple Javascript code for Jasmine Test Framework

Let’s consider below Javascript code. It simply declares a person object with few properties and method to get full name and change Age.

Its time to see how we can write a test method using Jasmine Framework.

Above code snippet shows how we are using describe, it and expect methods provided by Jasmine framework.

Let’s create a sample HTML page which will load Jasmine Framework, our Javascript code and Test method to Test our code.

Below is our files and folders structure

Below is the output of our example. As all test passed, we don’t see any error

In case, if some method fails test execution, then it would show error report like below image

First 25 minutes of below video is basics of Jasmine Test Framework with same example as of this post.

You can download latest version of soapUI from here.

The WSDL file defines the Web service that is available to you. Your development platform uses this WSDL to generate an API to access the Force.com Web service it defines. You can either obtain the WSDL file from your organization’s Salesforce administrator or you can generate it yourself if you have access to the WSDL download page in the Salesforce user interface. You can navigate to the most recent WSDL for your organization from Setup by clicking “Develop | API | Enterprise WSDL” and download it.

Create new soapUI project by navigating to “File | New soapUI Project“. Provide project name and address of WSDL file downloaded from Salesforce.

Login to Salesforce using soapUI

In newly created project, navigate to “login” binding and double click on Request1.

It will open split panel, left side contains sample request and right side contains response. We will be provided with sample request and need to enter required arguments, in this case username and password. Once done, click on green arrow above left panel, you would be presented with response on right panel (as shown in below image).

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:enterprise.soap.sforce.com">
   <soapenv:Header>
      <urn:LoginScopeHeader>
         <urn:organizationId></urn:organizationId>
         <!--Optional:-->
         <urn:portalId></urn:portalId>
      </urn:LoginScopeHeader>
   </soapenv:Header>
   <soapenv:Body>
      <urn:login>
         <urn:username>user@jitendra.com</urn:username>
         <urn:password>SamplePassword</urn:password>
      </urn:login>
   </soapenv:Body>
</soapenv:Envelope>

copy “sessionId” and “serverURL” from response, as we will need it to test other methods.

Query Salesforce records using soapUI and SOQL

Now, open “query” soap binding from soapUI project menu and update URL with server URL returned in above login call.

Sample XML request in soapUI to get records using SOQL

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:enterprise.soap.sforce.com">
   <soapenv:Header>
      <urn:PackageVersionHeader>
         <!--Zero or more repetitions:-->
         <urn:packageVersions>
            <urn:majorNumber>1</urn:majorNumber>
            <urn:minorNumber>1</urn:minorNumber>
            <urn:namespace></urn:namespace>
         </urn:packageVersions>
      </urn:PackageVersionHeader>
      <urn:MruHeader>

      </urn:MruHeader>
      <urn:QueryOptions>
         <!--Optional:-->
         <urn:batchSize>50</urn:batchSize>
      </urn:QueryOptions>
      <urn:SessionHeader>
         <urn:sessionId>00DU000000 0Mpcl!AQ 4AQMh.Hk2</urn:sessionId>
      </urn:SessionHeader>
   </soapenv:Header>
   <soapenv:Body>
      <urn:query>
         <urn:queryString>SELECT ID FROM Account</urn:queryString>
      </urn:query>
   </soapenv:Body>
</soapenv:Envelope>

Sample response from soapUI

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns="urn:enterprise.soap.sforce.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:sf="urn:sobject.enterprise.soap.sforce.com">
   <soapenv:Header>
      <LimitInfoHeader>
         <limitInfo>
            <current>106</current>
            <limit>15000</limit>
            <type>API REQUESTS</type>
         </limitInfo>
      </LimitInfoHeader>
   </soapenv:Header>
   <soapenv:Body>
      <queryResponse>
         <result>
            <done>true</done>
            <queryLocator xsi:nil="true"/>
            <records xsi:type="sf:Account">
               <sf:Id>001U000001SxeQQIAZ</sf:Id>
            </records>
            <records xsi:type="sf:Account">
               <sf:Id>001U000001SxeQRIAZ</sf:Id>
            </records>
            <records xsi:type="sf:Account">
               <sf:Id>001U000001SxeRGIAZ</sf:Id>
            </records>
            <size>3</size>
         </result>
      </queryResponse>
   </soapenv:Body>
</soapenv:Envelope>

In same way, we can use any other standard or custom WSDL using soapUI.

What is Selenium 

Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese)[1] to write tests in a number of popular programming languages, including Java, C#, Groovy, Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers like firefox, Chrome, Internet explorer. Selenium deploys on Windows, Linux and Macintosh platforms.

How Selenium can benefit me 

Its not only Automation testing where you can leverage selenium. You can use this tool to move some manual changes from one Salesforce organization to another, to avoid preparing test data every time when sand box is refreshed and so on.. usability is endless.

Installing Selenium

1. Download and install Firefox browser
2. Add Selenium IDE Plugin for Firefox from official Selenium download website

Once Selenium plugin is installed in Firefox we can launch Selenium IDE and it will look like below screen

As you can see in above image, red circle icon is used to record step and once it is recorded, can be re-run using green symbol. Complete step are explained in Video tutorial.

Error : Selenium element not found

Chances are very high, where we will receive error in selenium script about “Element not found”. This is because if some content is loaded via Ajax, Selenium doesnt know that it needs to wait. There are many ways to handle it, but for me “waitForElementPresent” works in most cases.

 Selenium Test Case code snippet

Video Tutorial