Salesforce QA Automation

Run Salesforce test scenarios using the Crank BDD framework.

Test your Salesforce Workflow and Process Builder automation as rigorously as you test your Apex code.

Salesforce Alert QA

Make sure Account owners receive alerts for high priority cases.

- step: Given I create a Salesforce Case object with...
  data:
    SuppliedName: High Priority Case (Test)
    Priority: High
    AccountId: '{{Fixtures.Accounts.PlatinumSLA.Id}}'
- step: Then there should be 1 email in mailgun for {{Fixtures.Users.PlatinumSLA.Email}}
  failAfter: 60
- step: And the subject of the 1st mailgun email for {{Fixtures.Users.PlatinumSLA.EmailAddress}} should contain High Priority Case Alert

Salesforce Lead Sync QA

Make sure lead updates are synced back to marketing automation.

- step: Given I create a Salesforce Lead with...
  data:
    Email: '{{Test.Email}}'
    FirstName: '{{Test.GivenName}}'
    LastName: '{{Test.FamilyName}}'
    Company: '{{Test.Company}}'
- waitFor: 60
  step: Then the Status__c field on Marketo Lead {{Test.Email}} should be Open - Not Contacted
- step: And when I update the Salesforce Lead object identified by Id {{salesforce.lead.Id}} with...
  data:
    Status: Working - Contacted
- waitFor: 60
  step: Then the Status__c field on Marketo Lead {{Test.Email}} should be Working - Contacted

What is Crank?

Crank is a BDD test automation framework for SaaS-based business technology.

Developer Getting Started Hosted QA Automation for Business Users

Installing and Authenticating this Cog

Once you've successfully installed Crank you can install this Cog by running the following:

$ crank cog:install automatoninc/salesforce

You will be asked for the following authentication details on installation. To avoid prompts in a CI/CD context, you can provide the same details as environment variables.

Expected Authentication Details
Field	Install-Time Environment Variable	Description
`instanceUrl ^*`	`CRANK_AUTOMATONINC_SALESFORCE__INSTANCEURL`	Login/instance URL (e.g. https://na1.salesforce.com)
`clientId ^*`	`CRANK_AUTOMATONINC_SALESFORCE__CLIENTID`	OAuth2 Client ID
`clientSecret ^*`	`CRANK_AUTOMATONINC_SALESFORCE__CLIENTSECRET`	OAuth2 Client Secret
`username ^*`	`CRANK_AUTOMATONINC_SALESFORCE__USERNAME`	Username
`password ^*`	`CRANK_AUTOMATONINC_SALESFORCE__PASSWORD`	Password

You can always re-authenticate by running the following command.

$ crank cog:auth automatoninc/salesforce

Further Auth Details Here

Salesforce Test Steps

Create a Salesforce Account ^Action

Use this step in a Scenario file like this:

- step: When I create a salesforce account
  data:
    account:
      field: value

Expected Step Input
ID	Type	Description
`account ^*`	Map/Object	A map of field names to field values

Exposed Dynamic Tokens
Token	Type	Description
`{{salesforce.account.Id}}`	String	Account's SalesForce ID

Create a Salesforce Contact ^Action

Use this step in a Scenario file like this:

- step: When I create a salesforce contact
  data:
    contact:
      field: value

Expected Step Input
ID	Type	Description
`contact ^*`	Map/Object	A map of field names to field values

Exposed Dynamic Tokens
Token	Type	Description
`{{salesforce.contact.Id}}`	String	Contact's SalesForce ID

Create a Salesforce Lead ^Action

Use this step in a Scenario file like this:

- step: When I create a salesforce lead
  data:
    lead:
      field: value

Expected Step Input
ID	Type	Description
`lead ^*`	Map/Object	A map of field names to field values

Exposed Dynamic Tokens
Token	Type	Description
`{{salesforce.lead.Id}}`	String	Lead's SalesForce ID

Create a Salesforce Object ^Action

Use this step in a Scenario file like this:

- step: When I create a salesforce {{objName}} object
  data:
    salesforceObject:
      field: value

Expected Step Input
ID	Type	Description
`objName ^*`	String	Salesforce object name
`salesforceObject ^*`	Map/Object	where keys represent object field names as represented in the SFDC API

Exposed Dynamic Tokens
Token	Type	Description
`{{salesforce.salesforceObject.Id}}`	String	Object's SalesForce ID

Create a Salesforce Opportunity ^Action

Use this step in a Scenario file like this:

- step: When I create a salesforce opportunity
  data:
    opportunity:
      field: value

Expected Step Input
ID	Type	Description
`opportunity ^*`	Map/Object	A map of field names to field values

Exposed Dynamic Tokens
Token	Type	Description
`{{salesforce.opportunity.Id}}`	String	Opportunity's SalesForce ID

Delete a Salesforce Account ^Action

Use this step in a Scenario file like this:

- step: Finally, delete the salesforce account with {{field}} {{identifier}}

Expected Step Input
ID	Type	Description
`field ^*`	String	the name of the field used to identify the account
`identifier ^*`	Any Scalar	the value of the field

Exposed Dynamic Tokens
Token	Type	Description
`{{salesforce.account.Id}}`	String	Account's SalesForce ID

Delete a Salesforce Contact ^Action

Use this step in a Scenario file like this:

- step: Finally, delete the {{email}} salesforce contact

Expected Step Input
ID	Type	Description
`email ^*`	Email Address	Contact's Email Address

Exposed Dynamic Tokens
Token	Type	Description
`{{salesforce.contact.Id}}`	String	Contact's SalesForce ID

Delete a Salesforce Lead ^Action

Use this step in a Scenario file like this:

- step: Finally, delete the {{email}} salesforce lead

Expected Step Input
ID	Type	Description
`email ^*`	Email Address	Lead's email address

Exposed Dynamic Tokens
Token	Type	Description
`{{salesforce.lead.Id}}`	String	Lead's SalesForce ID

Delete a Salesforce Object ^Action

Use this step in a Scenario file like this:

- step: Finally, delete the salesforce {{objName}} object with id {{id}}

Expected Step Input
ID	Type	Description
`objName ^*`	String	Salesforce Object name
`id ^*`	String	Object ID

Exposed Dynamic Tokens
Token	Type	Description
`{{salesforce.salesforceObject.Id}}`	String	Object's SalesForce ID

Delete a Salesforce Opportunity ^Action

Use this step in a Scenario file like this:

- step: Finally, delete the salesforce opportunity with {{field}} {{identifier}}

Expected Step Input
ID	Type	Description
`field ^*`	String	the name of the field used to identify the opportunity
`identifier ^*`	Any Scalar	the value of the field

Exposed Dynamic Tokens
Token	Type	Description
`{{salesforce.opportunity.Id}}`	String	Opportunity's SalesForce ID

Update a Salesforce Object ^Action

Use this step in a Scenario file like this:

- step: When I update the salesforce {{objName}} object identified by id {{identifier}}
  data:
    salesforceObject:
      field: value

Expected Step Input
ID	Type	Description
`objName ^*`	String	Salesforce object name
`identifier ^*`	String	Salesforce object ID
`salesforceObject ^*`	Map/Object	where keys represent object field names as represented in the SFDC API

Exposed Dynamic Tokens
Token	Type	Description
`{{salesforce.salesforceObject.Id}}`	String	Object's SalesForce ID

Check a field on a Salesforce Account ^Assertion

Use this step in a Scenario file like this:

- step: Then the {{field}} field on salesforce account with {{idField}} {{identifier}} should {{operator}} {{expectedValue}}

Expected Step Input
ID	Type	Description
`idField ^*`	String	The field used to search/identify the account
`identifier ^*`	Any Scalar	The value of the id field to use when searching
`field ^*`	String	The name of the field to check
`operator`	String	Check Logic (be, not be, contain, not contain, be greater than, be less than, be set, not be set, be one of, or not be one of)
`expectedValue`	Any Scalar	The expected value of the field

Exposed Dynamic Tokens
Token	Type	Description
`{{salesforce.account.Id}}`	String	Account's SalesForce ID
`{{salesforce.account.CreatedDate}}`	ISO 8601 Datetime	Account's Created Date
`{{salesforce.account.LastModifiedDate}}`	ISO 8601 Datetime	Account's Last Modified Date
`{{salesforce.account.*}}`	*	This step may expose additional dynamic tokens representing values on the account, depending on how you've configured the underlying system.

Check a field on a Salesforce Campaign Member ^Assertion

Use this step in a Scenario file like this:

- step: Then the salesforce lead {{email}} should have campaign member {{field}} {{operator}} {{expectedValue}} on campaign {{campaignId}}

Expected Step Input
ID	Type	Description
`email ^*`	Email Address	Lead's email address
`campaignId ^*`	String	Campaign ID
`field ^*`	String	Field name to check
`operator`	String	Check Logic (set to, not set to, containing, not containing, greater than, less than, set, not set, set to one of, or not set to one of)
`expectedValue`	Any Scalar	Expected field value

Exposed Dynamic Tokens
Token	Type	Description
`{{salesforce.campaignMember.Id}}`	String	Campaign Member's SalesForce ID
`{{salesforce.campaignMember.CreatedDate}}`	ISO 8601 Datetime	Campaign Member's Created Date
`{{salesforce.campaignMember.LastModifiedDate}}`	ISO 8601 Datetime	Campaign Member's Last Modified Date
`{{salesforce.campaignMember.CampaignId}}`	String	Campaign Member's Campaign Id
`{{salesforce.campaignMember.LeadId}}`	String	Campaign Member's Lead Id
`{{salesforce.campaignMember.ContactId}}`	String	Campaign Member's Contact Id
`{{salesforce.campaignMember.LeadOrContactId}}`	String	Campaign Member's Lead or Contact Id
`{{salesforce.campaignMember.*}}`	*	This step may expose additional dynamic tokens representing values on the campaignMember, depending on how you've configured the underlying system.

Check a field on a Salesforce Contact ^Assertion

Use this step in a Scenario file like this:

- step: Then the {{field}} field on salesforce contact {{email}} should {{operator}} {{expectedValue}}

Expected Step Input
ID	Type	Description
`email ^*`	Email Address	Contact's email address
`field ^*`	String	Field name to check
`operator`	String	Check Logic (be, not be, contain, not contain, be greater than, be less than, be set, not be set, be one of, or not be one of)
`expectedValue`	Any Scalar	Expected field value

Exposed Dynamic Tokens
Token	Type	Description
`{{salesforce.contact.Id}}`	String	Contact's SalesForce ID
`{{salesforce.contact.CreatedDate}}`	ISO 8601 Datetime	Contact's Created Date
`{{salesforce.contact.LastModifiedDate}}`	ISO 8601 Datetime	Contact's Last Modified Date
`{{salesforce.contact.*}}`	*	This step may expose additional dynamic tokens representing values on the contact, depending on how you've configured the underlying system.

Check a field on a Salesforce Lead ^Assertion

Use this step in a Scenario file like this:

- step: Then the {{field}} field on salesforce lead {{email}} should {{operator}} {{expectedValue}}

Expected Step Input
ID	Type	Description
`email ^*`	Email Address	Lead's email address
`field ^*`	String	Field name to check
`operator`	String	Check Logic (be, not be, contain, not contain, be greater than, be less than, be set, not be set, be one of, or not be one of)
`expectedValue`	Any Scalar	Expected field value

Exposed Dynamic Tokens
Token	Type	Description
`{{salesforce.lead.Id}}`	Number	Lead's SalesForce ID
`{{salesforce.lead.CreatedDate}}`	ISO 8601 Datetime	Lead's Created Date
`{{salesforce.lead.LastModifiedDate}}`	ISO 8601 Datetime	Lead's Last Modified Date
`{{salesforce.lead.*}}`	*	This step may expose additional dynamic tokens representing values on the lead, depending on how you've configured the underlying system.

Check a field on a Salesforce Object ^Assertion

Use this step in a Scenario file like this:

- step: Then the {{field}} field on salesforce {{objName}} object with id {{id}} should {{operator}} {{expectedValue}}

Expected Step Input
ID	Type	Description
`objName ^*`	String	Salesforce object name
`id ^*`	String	Object ID
`field ^*`	String	Field name to check
`operator ^*`	String	Check Logic (be, not be, contain, not contain, be greater than, be less than, be set, not be set, be one of, or not be one of)
`expectedValue`	Any Scalar	Expected field value

Exposed Dynamic Tokens
Token	Type	Description
`{{salesforce.salesforceObject.Id}}`	Number	Object's SalesForce ID
`{{salesforce.salesforceObject.CreatedDate}}`	ISO 8601 Datetime	Object's Created Date
`{{salesforce.salesforceObject.LastModifiedDate}}`	ISO 8601 Datetime	Object's Last Modified Date
`{{salesforce.salesforceObject.*}}`	*	This step may expose additional dynamic tokens representing values on the salesforceObject, depending on how you've configured the underlying system.

Check a field on a Salesforce Opportunity ^Assertion

Use this step in a Scenario file like this:

- step: Then the {{field}} field on salesforce opportunity with {{idField}} {{identifier}} should {{operator}} {{expectedValue}}

Expected Step Input
ID	Type	Description
`idField ^*`	String	The field used to search/identify the opportunity
`identifier ^*`	Any Scalar	The value of the id field to use when searching
`field ^*`	String	The name of the field to check
`operator`	String	Check Logic (be, not be, contain, not contain, be greater than, be less than, be set, not be set, be one of, or not be one of)
`expectedValue`	Any Scalar	The expected value of the field

Exposed Dynamic Tokens
Token	Type	Description
`{{salesforce.opportunity.Id}}`	String	Opportunity's SalesForce ID
`{{salesforce.opportunity.CreatedDate}}`	ISO 8601 Datetime	Opportunity's Created Date
`{{salesforce.opportunity.LastModifiedDate}}`	ISO 8601 Datetime	Opportunity's Last Modified Date
`{{salesforce.opportunity.*}}`	*	This step may expose additional dynamic tokens representing values on the opportunity, depending on how you've configured the underlying system.

Check Salesforce Campaign Membership ^Assertion

Use this step in a Scenario file like this:

- step: Then the salesforce lead {{email}} should be a member of campaign {{campaignId}}

Expected Step Input
ID	Type	Description
`email ^*`	Email Address	Lead's email address
`campaignId ^*`	String	Campaign ID

Exposed Dynamic Tokens
Token	Type	Description
`{{salesforce.campaignMember.Id}}`	String	Campaign Member's SalesForce ID
`{{salesforce.campaignMember.CreatedDate}}`	ISO 8601 Datetime	Campaign Member's Created Date
`{{salesforce.campaignMember.LastModifiedDate}}`	ISO 8601 Datetime	Campaign Member's Last Modified Date
`{{salesforce.campaignMember.CampaignId}}`	String	Campaign Member's Campaign Id
`{{salesforce.campaignMember.LeadId}}`	String	Campaign Member's Lead Id
`{{salesforce.campaignMember.ContactId}}`	String	Campaign Member's Contact Id
`{{salesforce.campaignMember.LeadOrContactId}}`	String	Campaign Member's Lead or Contact Id
`{{salesforce.campaignMember.*}}`	*	This step may expose additional dynamic tokens representing values on the campaignMember, depending on how you've configured the underlying system.

Missing a Step You Need?

This Cog is open source! Your contributions are welcome and encouraged.

Contribute on GitHub Join the Crank Spectrum Community