EagerTester
Occasional Contributor
Joined 3 years ago
User Profile
User Widgets
Contributions
Re: SessionCreator /Timeout option not firing EventControl_OnTimeout
Thanks for the reply. So it seems as though there is no way to execute steps when SessionCreator /Timeout has been reached. There are other parameters to export the log. I am aware of this, and am saving the log file locally. However I need to copy it to Azure storage once the project has finished running. It seems as though this is not achievable using the /Timeout option.SessionCreator /Timeout option not firing EventControl_OnTimeout
Hello! I am using SessionCreator to run a project suite, and am passing in a /Timeout variable. The project suite stops as expected when it hits the timeout value, but it does not fire EventControl_OnTimeout. Is it supposed to? https://support.smartbear.com/testcomplete/docs/working-with/automating/session-creator/index.html#timeout SessionCreator doco doesnt say that it does, It only says "If the testing session is still running after the timeout has elapsed, the utility will stop the session and report an error. The other tests will be canceled and TestComplete will be closed." https://support.smartbear.com/testcomplete/docs/reference/events/ontimeout.html The OnTimeoutEvent doco says "Occurs when a timeout expires in a project or in a project suite.". Is this the same as timing out a SessionCreator run? I am aware that Timeouts can be set for each test item or project within a project suite, but that is not what I am after. I am after a global event triggered by the parameter I am passing in. My goal is that when the timeout value is hit, to be able to save the logs and copy them somewhere, and also perform additional operations BEFORE SessionCreator/TestExecute is closed, Thanks!Azure batch node DistributedCOM error when running SessionCreator
Hi, I am having an issue with running SessionCreator on Azure. Our automation setup uses Azure Batch to run Tasks on nodes. Each task will run the test project using SessionCreator on the node. The problem we are running in to, is that when the second task runs on a node, at some point the automation will stop running. Looking at our custom logs we can see that just after one of the automated tests runs, a DistributedCOM error occurs: The above issue is happening regularly on the second Task that runs (second run off SessionCreator) on the same node. I am wondering has anyone encountered anything like this before? I am still unsure if this is a SessionCreator issue or an Azure issue. Thanks for any advice!SessionCreator Execution Logs
Hi there, Does SessionCreator.exe output any execution or operational logs? I'm running it on Azure on nodes in a pool. For some reason I can't figure out, one of the tasks times out, because (I think) SessionCreator/TE has crashed. When I connect to the node myself, I can see the last test that was ran from a log I am writing to during project suite execution, but I can't see why it stopped/crashed, as there has been no mht log produced. The Event Viewer also has no information at the time that the last test ran, which is around where I am expecting SessionCreator/TE to have crashed. Thanks! :)
