Completed

List of execution attributes

Is it possible to grab test execution data like other automation frameworks. i.e. Listener class implementation. What are the different details that we can extract and what are they?

Basically we want to know about how we can get the test details like  test_case_id, test_suite_id, test_suite_name, execution_time, execution_start_time_stamp, execution_end_time_stamp etc. 

We want to send this information over a Post API call   for our custom reporting purposes.

0
7 comments
Avatar
Jonathan Hotz

Hello, sri vamsi.

If you run test cases via execution set you can use callback section of it.
- Create REST connection that calls your server endpoint.
- Put required execution info properties to REST connection body in the format you need (e.g. JSON, XML).
- Go to Execution Set "Callbacks" section and setup it to use your REST connection on ANY result of Test Case execution.

So as soon as each test case execution is finished platform will call your REST connection and send execution variables you put into it.

At this moment we provide support for next test case execution variables in callback:
@test_case_execution_id
@test_case_execution_video_url
@test_case_execution_image_url
@test_case_execution_log_url
@test_case_execution_status
@test_case_execution_duration
@test_case_execution_defect_tracking_id

You can put it inside your callback REST connection as you usually do for test cases.

 

If you don't want to send details as execution callback or you want to get extended details use our API, please.

Documentation is here: https://platform.subject-7.com/spec/index.html

 

We plan to extend API with possibility to get suite and folder info in one of future releases.

0
Comment actions Permalink
Avatar
sri vamsi

Yeah we did all these and here is our JSON body for the Rest API call.

We need help in getting the missing info in the JSON body namely:"testCaseName","testCaseDescription","suiteName","teststartDateTime","testEndDateTime" and "testStatus"

{
"testCaseId" : "@test_case_execution_id",

"status": "@test_case_execution_status",

"testCaseName": ?

"testCaseDescription": ?

"suiteId": "@execution_set_id",

"suiteName": ?

"teststartDateTime": ?

"testEndDateTime": ?

"executionTime": @test_case_execution_duration

"testStatus": ?

}

0
Comment actions Permalink
Avatar
Jonathan Hotz

We will provide these properties in one of future releases.

0
Comment actions Permalink
Avatar
Rex Feizi

Hi, 

 

We are targetting these values to be added as part of our 8.12.0 or 8.12.1 release, which should be available by May 10th, 

 

Hope this helps. 

0
Comment actions Permalink
Avatar
Jonathan Hotz

sri vamsi, we have added next fields to test case execution callback and test case execution API call:

  • test case name
  • test case comments (description)
  • test suite name
  • execution set name
  • test case execution start date
  • test case execution end date
  • test case actual duration

It will be available in release 8.11.3 which should be available in few days.

 

Questions to you:

1. When you referred to testStatus field did you mean Test case execution status? This attribute already exists as @test_case_execution_status and you have already pointed to it in status field of your JSON request body.

2. You have field "testCaseId" : "@test_case_execution_id",  but test case ID and test case execution ID are different parameters. Do you need to have test case ID even though we have already added Test Case Name?

3. You have field "suiteId": "@execution_set_id", but suite ID and execution set ID are different parameters. Do you need to have suite ID even though we have already added Suite Name?

0
Comment actions Permalink
Avatar
Rex Feizi

The above request has made it to 8.11.3 and will be available in the new few days. I'll keep you posted on this thread. 

0
Comment actions Permalink
Avatar
Rex Feizi

Sri, 

Your enhancement requested was addressed in 8.11.3 that is in production now. 

Would you please comment as to if this satisfied your requirement. 

Thanks, 

--Rex

0
Comment actions Permalink

Please sign in to leave a comment.