ON24 QA Automation
Run ON24 test scenarios using the Crank BDD framework.
![ON24 Logo](/img/cogs/on24.png)
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.
Field | Install-Time Environment Variable | Description |
---|---|---|
clientId * | CRANK_AUTOMATONINC_ON24__CLIENTID | Client ID |
tokenKey * | CRANK_AUTOMATONINC_ON24__TOKENKEY | Token Key |
tokenSecret * | CRANK_AUTOMATONINC_ON24__TOKENSECRET | Token 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
ID | Type | Description |
---|---|---|
eventId * | Number | Event ID |
registrant * | Map/Object | A Map of registrant fields and their values. |
Token | Type | Description |
---|---|---|
{{on24.registrant.eventuserid}} | Number | Event User ID |
{{on24.registrant.createtimestamp}} | ISO 8601 Datetime | Registrant create date/time. |
{{on24.registrant.email}} | Email Address | Registrant'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}}
ID | Type | Description |
---|---|---|
email * | Email Address | Registrant's email address |
eventId * | Number | Event ID |
Token | Type | Description |
---|---|---|
{{on24.registrant.eventuserid}} | Number | Event User ID |
{{on24.registrant.email}} | Email Address | Registrant'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}}
ID | Type | Description |
---|---|---|
email * | Email Address | Registrant's email address |
eventId * | Number | Event 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 |
Token | Type | Description |
---|---|---|
{{on24.registrant.eventuserid}} | Number | Event User ID |
{{on24.registrant.createtimestamp}} | ISO 8601 Datetime | Registrant create date/time. |
{{on24.registrant.email}} | Email Address | Registrant'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