jkrolczySuper ContributorJoined 12 years ago281 Posts79 LikesLikes received20 SolutionsView All Badges
ContributionsMost RecentMost LikesSolutionsADO Pipeline Execution Fail issue after TC\TE upgrade I have noticed this issue after some past TC\TE upgrades. Once I have completed the TC\TE upgrades and see that TC\TE open up after upgrading I'll then go to test that an ADO pipeline starts up correctly. Initially the ADO pipeline fails with: Cmd.exe exited with code '2147483647'. My ADO pipeline did work prior to the upgrade. In debugging the cmd line structure that I am sending to the Agent I have determined that if I execute the following manually on my Hyper-V From a CMD window: "C:\Program Files (x86)\SmartBear\TestExecute 15\Bin\TestExecute.exe" "C:\Program Files (x86)\SmartBear\TestComplete 15\Bin\TestComplete.exe" Just to be sure TC\TE doing open up like it should ... TC\TE will start up but will provide this Error pop-up respectively per version I ran: Click 'OK' - TC\TE completes and opens up like it should. I'll close TC\TE. Going back to running my ADO pipeline, it will execute like it should. I do need to test this on the x64 version of TC\TE to see if the same issue occurs. Anyone have this issue ? I do need to open an ticket on this for Dev to look into. Re: ADO Pipeline Fails with Exit Code '2147483647' and Upgrading to TC/TE 15.75 Issue still seen in TC\TE 15.76 I have down graded back to 15.74 Re: Ctrl-Click Navigation issue to correct location of declaration\routine The above suggestions did not correct my issue. Playing with this issue more and remembering a long, long time ago. When I had code modules and the function\methods named the same like above, this issue would be seen. The way I corrected it was to either rename the code module or the function\method name. This would clear up the issue and allow ctrl-click navigation to work correctly. A little bug here? Auto fwk adjusted and code checked in. All working now. Re: Ctrl-Click Navigation issue to correct location of declaration\routine Also, I can go directly to the code for this test script: TC538453() And run the script directly with no issues. Ctrl-Click Navigation issue to correct location of declaration\routine I am using TC 15.76 and tried this on TC15.74 - same issue When in my automation fwk, the ability to ctrl-click on function name and taken to where it is declared is being flakey. A majority of my test scripts direct me correctly, but I have a few that direct me to the top of my test script and not to the correct location of declaration\routine. Here is a portion of how I call the test scripts in my package: // Module Testing // ---------------------- RTC538124(); - ctrl-click correctly to the declaration location of function\routine TC538453(); - issue with ctrl-click RTC538659(); - ctrl-click correctly to the declaration location of function\routine TC537950(); - ctrl-click correctly to the declaration location of function\routine Here is a portion of my test script: //USEUNIT RM_CommonFunctions (ctrl-click incorrectly takes me here) //USEUNIT RulesManagerMainWindowFunctions //USEUNIT RM_ManageUsersWndFunctions //USEUNIT RM_MainMenuFunctions //USEUNIT RM_TabFunctions //USEUNIT NEW_RM_Job_Monitor //USEUNIT NEW_RM_SearchEdits_Modules //USEUNIT NEW_RM_ModuleWorkSpace //USEUNIT RM_VersionHistoryWindow // ================================================ // Function: TC538124() - qTCID 50 // // // Edited by : // // Description: // This script performs that following steps: // // // ================================================ function TC538453() (ctrl-click should take me here) { // --- Results File Name --- var DateTimeLabel = getFileNameDateTimeLabel(); ... When I try to run a package of scripts, when executing this test script in the package, it provides the following error: Object doesn't support this property or method How can I correct this ctrl-click function issue to find the declaration\rountine correctly ? When in this test script, the routine textbox is blank when doing the ctrl-click. The dropdown for the Desired Routine area does contain the test script function name. Anyone seen this? Have a suggestion or solution to before I open a Support ticket? SolvedRe: TestComplete Support Ticket Not Being Fixed What was the issue you reported ? Re: Basic actions taking significantly longer when run as part of ADO pipeline Anything else running in the background on the VM during the time of test script(s) execution? What version of TC\TE are you using ? OS of the VM ? RAM ? Browser being used ? TC\TE - ObjectSpy issue with latest MS Edge 138.0.3351.121 Just checking to see if others experience this issue. For the most part, the rest of the products I automate and their frameworks do not have this issue. I have one product, that does not change that must from developer changes. It has always worked until a few months back when ... Scripts that worked previously are failing due to TC\TE unable to penetrate the webpage to find the web elements as usual. Scripts can log into the application, but from there ... ObjectSpy can only outline the outer boundary. Manually going into Object Browser with the web page open, I can see and go the the page objects (highlight on screen) that the test script should be finding when running the script. But since not able to penetrate the web page and ObjectSpy red line outlines the outer panel, the value I am trying to enter into a text box jumps up to the MS Edge URL section. I have uninstalled/re-installed the latest TC\TE to verify issue still exists. TestExecute extention is in the Edge browser. I know MS Edge updated around this time period. This is issue is not encountered with Chrome, just MS Edge ? I had opened an IT ticket for this and worked with support, but no solution came from it. I am thinking of switching to using Chrome instead of MS Edge, but this issue bugs me for why it stopped working. I continue to try different things from day to day. This issue has killed my automation for this product. Suggestions? Has this issue been reported from others, and work-around or patches available? Re: ADO Pipeline Fails with Exit Code '2147483647' and Upgrading to TC/TE 15.75 I am not seeing this issue with TestComplete 15.76 Re: ADO Pipeline Fails with Exit Code '2147483647' and Upgrading to TC/TE 15.75 Now that TestComplete 15.76 is out, I'll being p[laying with that version to see if my issue has been resolved itself. I'll report back.