This is a short document highlighting the parameters of the exposed rest API for invoking automated scenario tests remotely:
Example service endpoint URL:
JobID - Unique Job ID/Run ID/Build number for the invocation (Used by the Deployment manager to separate runs across deployments, also passed as the run id to cloud providers for tracking)
Provider - STANDALONE | CBT | BROWSERSTACK Test service provider to use (or Test service cloud provider) ProviderAuthName - Auth name for the test service account ProviderAuthKey - Auth key for the test service account ProviderURL - Alternate test service provider URL (Optional - Generally used for local selenium hubs)
Browser - Browser to run the UI tests on BrowserVersion - Browser version to run the UI tests on Platform - OS platform to use PlatformVersion - OS Platform version to use ScreenResolution - Resolution of the test system screen to run the tests on
SUTURL - URL of the Pega system under test SUTUserID - Test operator ID from the Pega system under test SUTPassword - Password of the test operator ID from the Pega system under test
Note: If using cloud providers, please check their documentation on browsers, versions and platforms they support. This is in addition to the authname and the authkey that is provider specific. If running selenium hubs standalone or as part of a grid, please make sure to configure the grid capabilities to match the parameters being passed to the API.
We have created few Scenario tests in our Pega 8.4 instance using Scenario UI tests we have in Pega and we would like to execute them via REST API, can you please help us in terms of how the above mentioned service can be used.
For running scenario test cases through the above mentioned REST API, a third party tool is required. (CrossBrowserTesting, BrowserStack, SauceLabs or Selenium standalone/ Selenium Grid).
To know how to pass parameters for the REST API, when any one of the above mentioned third party tool access is available, please refer to appropriate article, which is mentioned in the first reply to this article. For ease of access, providing the same article links below.