Hi Ulrich,
Hope, I got your problem right...
Well, you may get the state of every job via its properties - https://support.smartbear.com/testcomplete/docs/reference/project-objects/items/network-suite/job/st...
As for the status (I guess that in the given case you understand it like passed/failed)...
On the one hand, it might be handy if job.Run() returns something like this.
But on the other hand:
-- While TestComplete well can be used for integration testing, its primary area is end-to-end testing (https://automationpanda.com/2017/10/14/bdd-101-unit-integration-and-end-to-end-tests/);
-- In the end-to-end testing we are checking not that some operation works, but that some task can be done. It is possible that some problem occurs while doing the task and this problem definitely must be reported to the test log. But if the task can be done, then it should be reported as 'passed with problems'. And then it is a job for the relevant people to triage the severity of the reported problem.
With the above in mind, I am not sure that simple Pass/Fail status is really meaningful result for the end-to-end tests.
Regards,
/Alex [Community Hero]
____
[Community Heroes] are not employed by SmartBear Software but
are just volunteers who have some experience with the tools by SmartBear Software
and a desire to help others. Posts made by [Community Heroes]
may differ from the official policies of SmartBear Software and should be treated
as the own private opinion of their authors and under no circumstances as an
official answer from SmartBear Software.
The [Community Hero] signature is used with permission by SmartBear Software.
https://community.smartbear.com/t5/custom/page/page-id/hall-of-fame
================================
