How To Test Rest Service In Pega Using Postman

Question

Member since 2020 3 posts

Morgan Stanley

Posted: Dec 23, 2020

Last activity: January 31, 2021

Posted: 23 Dec 2020 5:15 EST
Last activity: 31 Jan 2021 23:35 EST

Scenario test Residuum service non working in STANDALONE mode

Usecase:

Execute a scenario test suite using OOTB Residue service(/api/v1/testautomation/scenario and /api/v1/scenariotests/execute) and consume the response. Nosotros want to use information technology in test automation scripts.

Event:

Tried running the to a higher place mentioned rest service(Postal service method by giving all the necessary parameters) dominion by giving the scenario exam suite pxInsName and expecting a response with pass fail information. But, Response body is empty and response lawmaking is http 200. Sample request beneath.

request data

Analysis:

Residuum service is calling actvity pzExecuteScenarioTests which takes the to a higher place parameters and tries to get a ScenarioTestRunner and runs it. This lawmaking is neither giving exception nor executing the tests.

fetchedRunner is coming as false and

((com.pega.pegarules.priv.testautomation.IScenarioTestRunner)runner).runAll(); is not getting executed.

tried removing the if(fetechedRunner==truthful) check besides, all the same did not work.

Lawmaking snippet:

Usecase:

Execute a scenario examination suite using OOTB Remainder service(/api/v1/testautomation/scenario and /api/v1/scenariotests/execute) and swallow the response. We want to use it in examination automation scripts.

Effect:

Tried running the above mentioned residuum service(Mail service method past giving all the necessary parameters) dominion by giving the scenario exam suite pxInsName and expecting a response with laissez passer fail information. But, Response torso is empty and response lawmaking is http 200. Sample request below.

request data

Analysis:

Rest service is calling actvity pzExecuteScenarioTests which takes the above parameters and tries to get a ScenarioTestRunner and runs it. This code is neither giving exception nor executing the tests.

fetchedRunner is coming as fake and

((com.pega.pegarules.priv.testautomation.IScenarioTestRunner)runner).runAll(); is non getting executed.

tried removing the if(fetechedRunner==truthful) cheque as well, still did not work.

Lawmaking snippet:

runner = ((PegaAPI)tools).getScenarioTestRunner(); fetchedRunner = ((com.pega.pegarules.priv.testautomation.IScenarioTestRunner)runner).init(Provider, JobID, ProviderURL, ProviderAuthName, ProviderAuthKey, Browser, BrowserVersion, Platform, PlatformVersion, ScreenResolution, TestSuiteID, SUTURL, SUTUserID, SUTPassword);

if(fetchedRunner == truthful) { ((com.pega.pegarules.priv.testautomation.IScenarioTestRunner)runner).runAll(); }

Please help in resolving the issue.

***Edited past Moderator: Pooja Gadige to change content format from Discussion to Question***

Pega Platform 8.5.i DevOps Testing Applications

Moderation Team has archived post,

This thread is closed to hereafter replies. Content and links will no longer be updated. If y'all have the same/similar Question, please write a new Question.

Posted: 4 Jan 2021 1:14 EST

however looking for help on this.

Posted: one year ago

Updated: 1 yr ago

Posted: 5 Jan 2021 4:28 EST
Updated: 5 Jan 2021 4:37 EST

Hello Aditya, pitiful for the filibuster !

When we apply "Standalone" pick, nosotros must pass "ProviderURL" which is one of the inputs of the service as shown in pic that you shared above. This will be something like, "<host>:<port>/wd/hub". Too, for browser and platform capabilities we laissez passer the ones, that are supported past the standalone setup. To see this capabilities, first we can access "ProviderURL" from a browser, create a session from at that place, then check for the capabilities.

Also, brand sure to pass pxInsName of the Test suite properly. You lot can find it by, opening the examination suite, going to "Actions" menu, clicking on "View XML", searching for "pxInsName".

Posted: 7 January 2021 4:55 EST

Thanks Kavya for clarifying.

So fifty-fifty with standalone choice, nosotros need to requite a selenium grid hub url in the provider url.

Then does information technology mean in social club to run the scenario test through Residual api, we e'er need a third party provider(like selenium filigree, CBT, etc)?

How is running the scenario exam suite rule(from actions menu) different from executing it through REST service as it doesn't require a third party provider.

Accepted Solution

Posted: 1 year ago

Updated: 1 year agone

Posted: 18 Jan 2021 v:26 EST
Updated: 29 Jan 2021 seven:44 EST

@AdithyaK9774

For the outset question (Then does it mean in order to run the scenario test through Residual api, we always demand a tertiary party provider(like selenium filigree, CBT, etc)?), the answer is Yep.

For the 2d question(How is running the scenario test suite rule(from actions menu) different from executing information technology through Residue service as it doesn't require a third political party provider.), the answer is below..

When test cases are run from Test suite's Actions menu (or in general, test case run from dev studio), the infrastructure to run the test cases is the Bone on which nosotros are working and, the browser using which we accessed our application. EX: Windows ten, chrome(installed version). Basically these UI based Scenario tests need some infrastructure to become executed on. This infra includes (Bone, browser, desired screen resolution, etc..). And then, when it comes to test case execution using Balance service, it also needs some infrastructure to run our Scenario tests. To provide such infra there are tools bachelor on web like, CrossBrowserTesting, BrowserStack, etc. So, providing the details of one such tools is required to run test cases using REST service.

Posted: 29 Jan 2021 7:45 EST

@dhulk1 thanks for clarifying

Posted: 31 Jan 2021 23:35 EST