SalesLoft QA Automation

Run SalesLoft test scenarios using the Crank BDD framework.

SalesLoft Logo

Installing and Authenticating this Cog

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

$ crank cog:install automatoninc/salesloft

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
FieldInstall-Time Environment VariableDescription
apiKey *CRANK_AUTOMATONINC_SALESLOFT__APIKEYAPI Key

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

$ crank cog:auth automatoninc/salesloft
Further Auth Details Here

SalesLoft Test Steps

Create or update a SalesLoft person Action

Use this step in a Scenario file like this:

- step: When I create or update a salesloft person
  data:
    person:
      field: value
Expected Step Input
IDTypeDescription
person *Map/ObjectA map of field names to field values
Exposed Dynamic Tokens
TokenTypeDescription
{{salesloft.person.id}}NumberPerson's SalesLoft ID
{{salesloft.person.created_at}}ISO 8601 DatetimePerson's SalesLoft Created At
{{salesloft.person.updated_at}}ISO 8601 DatetimePerson's SalesLoft Updated At
{{salesloft.person.*}}*This step may expose additional dynamic tokens representing values on the person, depending on how you've configured the underlying system.

Delete a SalesLoft person Action

Use this step in a Scenario file like this:

- step: Finally, delete the {{email}} salesloft person
Expected Step Input
IDTypeDescription
email *Email AddressPerson's email address
Exposed Dynamic Tokens
TokenTypeDescription
{{salesloft.person.id}}NumberPerson's SalesLoft ID
{{salesloft.person.created_at}}ISO 8601 DatetimePerson's SalesLoft Created At
{{salesloft.person.updated_at}}ISO 8601 DatetimePerson's SalesLoft Updated At
{{salesloft.person.*}}*This step may expose additional dynamic tokens representing values on the person, depending on how you've configured the underlying system.

Check a field on a SalesLoft Person Assertion

Use this step in a Scenario file like this:

- step: Then the {{field}} field on salesloft person {{email}} should {{operator}} {{expectation}}
Expected Step Input
IDTypeDescription
email *Email AddressPerson's email address
field *StringField name to check
operator StringCheck 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)
expectation Any ScalarExpected field value
Exposed Dynamic Tokens
TokenTypeDescription
{{salesloft.person.id}}NumberPerson's SalesLoft ID
{{salesloft.person.created_at}}ISO 8601 DatetimePerson's SalesLoft Created At
{{salesloft.person.updated_at}}ISO 8601 DatetimePerson's SalesLoft Updated At
{{salesloft.person.*}}*This step may expose additional dynamic tokens representing values on the person, 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 GitHubJoin the Crank Spectrum Community