how to generate report at run time from test shell

[Quali-Community]

Hi,

We have a top level test which executes multiple tests.

Currently, we generate reports manually from 'test shell -> View Reports' after the test executaion.

We want to automate in creating the report once the test is finished, How can we achieve this please?

Thanks & Regards,

Raj.

---

 Rajasekaran veerichetti (rajasekaran.veerichetti) - 01/07/2022 11:46 AM

·  5574  ·

[Quali-Community]

you can pull reports by visiting the URL of a test, passing in the execution id

https://help.quali.com/Online%20Help/0.0/Portal/Content/CSP/JOB-SCHDL/View-Tst-Rprts.htm?Highlight=report

sample URL of test report:

http://<QUALI_SERVER>/Test/Report?reportId=<EXECUTION_ID>

example:

http://qs-il-lt-nattik/Test/Report?reportId=1a21798c-9d35-4d8a-960f-cbcef05156e8

as this URL is composed of the execution id, you can make an http request to this URL after being passed the execution id to pull down that report.

execution id is available as reserved variable inside testshell:

{executionDetails.ExecutionId}

the main test can't pull it's own report while it's running, but if you are calling sub tests, you can have main test pull those reports after test is done executing.

---

Natti Katz ([email protected]) - 01/09/2022 01:01 AM

·  5575  ·

[Quali-Community]

Hi Natti,

Thanks for your response.

We are running the tests from Testshell Studio on a different machine rather than server and not also not via Job Scheduler.

So where is the test report kept in the local machine please and how to access it from Test while running?

When tried to do Execution Query with Server option via Testshell studio, it say's 'no matching results found'. It looks like the report is only in the client machine.

Thanks & Regards,

Raj.

---

Rajasekaran veerichetti (rajasekaran.veerichetti) - 01/11/2022 11:00 AM

·  5578  ·

[Quali-Community]

there is a reserved keyword available in TestShell - executionDetails (it pairs will with the 'self' keyword)

	Call Stack: {self.CallStack}
	External Path: {self.ExternalPath}
	Interal Path: {self.InternalPath}
	Test Name: {self.Name}
	Execution ID: {executionDetails.ExecutionId}
	Job ID: {executionDetails.JobId}
	Root Execution ID: {executionDetails.RootExecutionId}
	Suite ID: {executionDetails.SuiteId}

When Ran, checked via TestShell Runner - Execution ID and Root Execution ID appear (in my case the same, but if the test was being called by someone else, as in your case, it should be that one).

Suite and Job ID's were blank (All Zeros, UUID 4 format)

---

TSI Support ([email protected]) - 07/11/2022 04:57 AM

·  5639  ·