jjackson150
Occasional Contributor
Joined 2 years ago
User Profile
User Widgets
Contributions
Re: "Unable to find the object Sys.Browser("chrome")" When Running Several Back to Back Tests
I'll add the additional WaitBrowser property, but it may take some time to confirm whether this fixed the issue or not. Personally, I don't believe it's a coincidence that the following test in the execution plan failed for the same reason, and the last test (where TC is closed/reopened) suddenly starts working again. We've seen this issue several times. Even while developing new tests. Thank you for the help."Unable to find the object Sys.Browser("chrome")" When Running Several Back to Back Tests
Hi SmartBear, When my team runs several tests back to back, we will occasionally receive the following error "Unable to find the object Sys.Browser("chrome")". This falsely fails the current test and prevents any subsequent tests in the execution plan from successfully running. TestComplete has to be restarted to fix this issue. We want to use the execution plan to run a series of tests, but to reliably run back to back tests, we have to reset TestComplete in-between tests. I've attached a screenshot of a test log showing where "Unable to find the object Sys.Browser("chrome")" starts failing our tests and how a new test (LoginTMS7_ChomeBeta) outside of the "Manual Transaction - Bulk" execution plan resolves the error.Re: Unable to Schedule Unattended Tests with Jenkins
AlexKaras rraghvani Thanks for the suggestions. Possible solutions A and B, could be a good option we adopt down the line. For the time being, if we connect to the remote desktop, we'll just need to make sure we disconnect from the RDP session using one of the disconnect options from the TestComplete documentation. (https://support.smartbear.com/testcomplete/docs/testing-with/running/via-rdp/keeping-computer-unlocked.html). I was incorrect in saying "They provide a solution where a batch file disconnects the session before running the tests, but not a solution that would allow me to keep a RDP session disconnected for multiple separate test runs".Re: Unable to Schedule Unattended Tests with Jenkins
rraghvani Yes, it runs as expected if I run the batch file manually. I would rather not use the batch file route, because I'll lose the benefits of the TestComplete plugin. Here's the simple batch file: @echo off REM Change to the TestComplete installation directory cd C:\Program Files (x86)\SmartBear\TestComplete 15\x64\Bin\ REM Launch TestComplete TestComplete.exe /run /project:"C:\Jenkins\workspace\QA_Server_Regression_Pipeline\Framework\Suite.pjs" This is being ran with TestComplete and yes, I've read through that documentation. It does not seem to provide solutions on how to run tests while the RDP session is disconnected. They provide a solution where a batch file disconnects the session before running the tests, but not a solution that would allow me to keep a RDP session disconnected for multiple separate test runs (e.g. nightly test runs) Thanks for your help, - JoshUnable to Schedule Unattended Tests with Jenkins
Our organization purchased a dedicated Windows 10 desktop to scheduled our TestComplete tests. I've developed a Jenkins pipeline using the TestComplete plugin. The pipeline and plugin executes our TC tests perfectly, but once we disconnect from the RDP (remote desktop) session, the tests fail, as the tests can longer interact with the GUI. I've investigated several solutions, but nothing has worked. The solution that aligns best with what we need, is this: https://community.smartbear.com/t5/TestComplete-Questions/The-operation-cannot-be-performed-because-the-user-session-is/m-p/206172#M4158 I attempted the solution in this community post and it almost worked! The Jenkins agent Windows service was successfully created and the agent is able to open a batch file, but it's unable to launch TestComplete (despite the log). [TestComplete] Launching the test runner. Everything in the logs look good, but when TC is supposed to launch, it never does. The test will sit in this state indefinitely. I've also created a wrapper script (e.g. batch file) that opens TestComplete and same result. Everything in the logs look good, but when TC is supposed to launch, it never does. The test will sit in this state indefinitely.
