zirka2
New Contributor
Joined 5 years ago
User Profile
User Widgets
Contributions
Re: [Integrate with Jenkins] Test runner exit code: -8
Dear qa_qed! Thanks for your reply, please let me know when you have any updates on your issue. Unfortunately, my issue has been present for more than a year ago. Previously i asked for some help at support, but they couldn't give me a proper solution, only asking me for more information - and now we have no support subscription. However, I don't know, did I introduce the issue correctly. I meant sometimes happens, a job fails with this -8 exit code stuff, but on another day, the same test passes, with exactly the same settings. When the job fails, I have no testcomplete report at all. Only Jenkins says in TestComplete report: "Failed to start"[Integrate with Jenkins] Test runner exit code: -8
Dear Community! I have an issue with running tests integrated in jenkins. The jobs run nightly, and i suppose it runs untill the defined timeout, and then exits, and marks the job failed. I have several tests defined, and sometimes there is an issue marked by the exit code: -8. The related console message: $ '"C:\Program Files (x86)\SmartBear\TestExecute 14\bin\TestCompleteService14.exe"' //LogonAndExecute //lDomain: "" //lName: "jenkins" //lPassword: ** //lTimeout: "5580000" //lUseActiveSession: "true" //lCommandLine: '""C:\Program Files (x86)\SmartBear\TestExecute 14\x64\bin\TestExecute.exe" C:\test.pjs /run /SilentMode /ForceConversion /ns /exit /ExportLog:C:\Jenkins\workspace\myJob\1654292692814.tclogx /ExportLog:C:\Jenkins\workspace\myJob\1654292692814.htmlx /ErrorLog:C:\Jenkins\workspace\myJob\1654292692814.txt /Timeout:5400 /project:Test /unit:TestScript /routine:testing /DoNotShowLog /JenkinsTCPluginVersion:2.8.1"' //lSessionScreenWidth: "1920" //lSessionScreenHeight: "1080" [TestComplete] Test runner exit code: -8 (An internal error occurred. Please contact SmartBear's Support Team). [TestComplete] [WARNING] Unable to find the log file "1654292692814.tclogx". [TestComplete] [WARNING] Unable to find the log file "1654292692814.htmlx". [TestComplete] [WARNING] Errors occurred during the test execution. [TestComplete] Marking the build as FAILED. [TestComplete] [WARNING] Unable to publish test results (xml data is empty). Sometimes one job/test is done correctly, sometimes the introduced issue heappens -- i mean there couldn't be problem with job/test configuration. I found some (maybe archive) posts reated to previous testexecute versions, unfortunately unsolved. Now i use Version: 14.81.217.11 , still having the issue. The other similar posts found: https://community.smartbear.com/t5/TestComplete-Questions/Integrate-with-Jenkins-can-not-find-log-file-error-and-failed/m-p/99688 https://community.smartbear.com/t5/TestComplete-Questions/Jenkins-and-TC-10-6-integration/m-p/161762 Does anyone have idea what to check, what might cause this issue?Add "link" parameter to Log.AppendFolder method
When creating a new log folder now, user cannot append an url, or other link to the root log folder, what would be related to the content of this row. The only possibility is, to create a new child massage, with a link. But it appears in a new row, and requires to drop down the root folder. It would be useful to avoid this unnecessary drop down action to see a link related to the root folder in the same row in "Link" column. As you can see in the attached picture, "https://smartbear.com/" URL could be in the upper folder.Re: Event handler doesn't triggered when my unexpected window appears
Dear Marsha_R! I didn't attach eventhandler code, because testcomplete never hit the eventhandler script. The attached error message shows the point, when testcomplete should call the eventhandler, but for me it seems like, the engine doesn't recognise it's an unexpected window event, only that the tested window is disabled. Additionally i followed the setting steps of event handling described like in the related section on this page: https://support.smartbear.com/articles/testcomplete/handling-unexpected-windows/ Thanks, BenjaminEvent handler doesn't triggered when my unexpected window appears
Dear Community! I'm struggling for a while with my issue, looking for some solution in former discussions. In my test project sometimes a kind of unexpected window appears during test run. In some cases it's easy to handle the situation by adding some extra lines to the scripts, which checks for the existance of that window. I mean, i have this window mapped in TesComplete Namemapping, and checking the .Exists() property, and do the necessary steps. But it's not so effective, having this high amount of mostly unnecessary waste of time. I tried to set up an event handler, followed the steps, described in manual for OnUnexpectedWindow event. I added a script, which should handle the event. But, what i see, testcomplete never calls this event handler, only exits with error attached in the picture. Is there any reason of this, or is there any additional parameter setting which i may have missed? Thank you all in advance, Benjamin
