ON24 QA Automation

Run ON24 test scenarios using the Crank BDD framework.

ON24 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/on24

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
clientId *CRANK_AUTOMATONINC_ON24__CLIENTIDClient ID
tokenKey *CRANK_AUTOMATONINC_ON24__TOKENKEYToken Key
tokenSecret *CRANK_AUTOMATONINC_ON24__TOKENSECRETToken Secret

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

$ crank cog:auth automatoninc/on24

ON24 Test Steps

Create an ON24 registrant Action

This step attempts to create a registrant for the given event ID.

Use this step in a Scenario file like this:

- step: When I create an ON24 registrant for event {{eventId}}
  data:
    registrant:
      field: value
Expected Step Input
IDTypeDescription
eventId *NumberEvent ID
registrant *Map/ObjectA Map of registrant fields and their values.
Exposed Dynamic Tokens
TokenTypeDescription
{{on24.registrant.eventuserid}}NumberEvent User ID
{{on24.registrant.createtimestamp}}ISO 8601 DatetimeRegistrant create date/time.
{{on24.registrant.email}}Email AddressRegistrant's e-mail address
{{on24.registrant.*}}*This step may expose additional dynamic tokens representing values on the registrant, depending on how you've configured the underlying system.

Forget an ON24 registrant Action

This step attempts to "forget" (or delete) a registrant for the given event ID.

Use this step in a Scenario file like this:

- step: When I forget that {{email}} registered for ON24 event {{eventId}}
Expected Step Input
IDTypeDescription
email *Email AddressRegistrant's email address
eventId *NumberEvent ID
Exposed Dynamic Tokens
TokenTypeDescription
{{on24.registrant.eventuserid}}NumberEvent User ID
{{on24.registrant.email}}Email AddressRegistrant's e-mail address

Check a field on an ON24 registrant Assertion

This step attempts to find an event registrant for the given event ID and email, then checks the value of a specified registrant field.

Use this step in a Scenario file like this:

- step: Then the {{field}} field on ON24 registrant {{email}} for event {{eventId}} should {{operator}} {{expectedValue}}
Expected Step Input
IDTypeDescription
email *Email AddressRegistrant's email address
eventId *NumberEvent ID
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)
expectedValue Any ScalarExpected field value
Exposed Dynamic Tokens
TokenTypeDescription
{{on24.registrant.eventuserid}}NumberEvent User ID
{{on24.registrant.createtimestamp}}ISO 8601 DatetimeRegistrant create date/time.
{{on24.registrant.email}}Email AddressRegistrant's e-mail address
{{on24.registrant.*}}*This step may expose additional dynamic tokens representing values on the registrant, 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