Phanindra
Occasional Contributor
Joined 5 years ago
User Profile
User Widgets
Contributions
Unable to push the code from local repository to remote bitbucket repository
I have created a local repository as per the instructions provided in the below link: https://support.smartbear.com/testcomplete/docs/working-with/integration/scc/bitbucket.html I am trying to push my code into remote bitbucket repository and I am getting following message in the output console: The timeout has expired. [Operation completed. Exit code: -2] Please find the attached document for more details.Solved903Views0likes1CommentRe: Getting Error: Unable to navigate to the URL/page while launching tests
mikef I was able to resolve this issue though this link: https://support.smartbear.com/testcomplete/docs/testing-with/running/via-rdp/in-minimized-window.html I have marked your comment as the solution since one of the links which you suggested leads to my link which I have mentioned above. Thanks a lot for your review comments, those things helped me a lot to learn the tool. Have a good day! Thanks! Phanindra4.9KViews2likes0CommentsRe: Getting Error: Unable to navigate to the URL/page while launching tests
mikef Please find the answers inline When you have the JNLP slave agent running, are you able to run tests on the node? - yes when I launch the slave agent running and open that VM through RDP connection then I can run my tests (please watch 2nd video) Is there perhaps some authentication step that needs to occur? - There is no need or problem with system authentication since the bowser and mongodb command prompt are already launched on that VM. Can you record/run a test on any other URL? - I have tried with other sample links like google, yahoo and ebay links, it works perfectly fine when I have my VM open through RDP but if I close the RDP session and run the jobs then again it will fail with the same reason.4.9KViews0likes2CommentsGetting Error: Unable to navigate to the URL/page while launching tests
I am unable to execute my tests when launched through a Jenkins job. Please find the environment details below: TestComplete (Server): 14.81.217.7 x64 TestExecute (VM): 14.81.217.11 Chrome Version (Server): 91.0.4472.77 Chrome Version (VM): 91.0.4472.77 License Details: TestComplete 14: node-locked TestExecute 14: floating, 1 seat Job Details: Run interactive user session is turned ON and running a specific project suite. Node Details: Launch method: Launch agent by connecting it to the master Internal data directory: remoting Scenario 1: Launch the VM through RDP session from the server machine and run the Jenkins job by keeping the VM session active then my tests will run. I can see the tests running through TestComplete chrome plugin. Scenario 2: Disconnect the VM and then run the jenkins job, after few minutes jenkins job will be marked as failure and I see following logs: ========================== Started by user admin Running as SYSTEM Building remotely on DESKTOP-73F1U9C in workspace C:\jenkins\agent\workspace\test [TestComplete] The test execution started (Packnet/Packnet). [TestComplete] Found TestComplete/TestExecute installations: Type: TE, Version: 14.81.217.11, Path: "C:\Program Files (x86)\SmartBear\TestExecute 14\x64\bin\TestExecute.exe" Type: TELite, Version: 14.81.217.50, Path: "C:\Program Files (x86)\SmartBear\TestExecuteLite 14\x64\bin\TestExecuteLite.exe" [TestComplete] Selected TestComplete/TestExecute installation: Type: TE, Version: 14.81.217.11, Path: "C:\Program Files (x86)\SmartBear\TestExecute 14\x64\bin\TestExecute.exe" [TestComplete] [WARNING] The node is connected via Java Web Start (JNLP). In this mode, the "Run interactive user session" property of the TestComplete Test step is ignored. TestComplete (or TestExecute) will work in the current user session. [TestComplete] Launching the test runner. $ '"C:\Program Files (x86)\SmartBear\TestExecute 14\x64\bin\SessionCreator.exe"' ExecuteProcess '/c:""C:\Program Files (x86)\SmartBear\TestExecute 14\x64\bin\TestExecute.exe"" "C:\PackNet_Automation_POC\Packnet.pjs" /run /SilentMode /ForceConversion /ns /exit "/ExportLog:C:\jenkins\agent\workspace\test\1622818571792.tclogx" "/ExportLog:C:\jenkins\agent\workspace\test\1622818571792.htmlx" "/ErrorLog:C:\jenkins\agent\workspace\test\1622818571792.txt" "/ExportLog:C:\jenkins\agent\workspace\test\1622818571792.mht" "/project:Packnet" /DoNotShowLog /JenkinsTCPluginVersion:2.6.2' [TestComplete] Test runner exit code: 2. [TestComplete] [WARNING] Error: Unable to navigate to the http://localhost/packnet/#/Login page.. [TestComplete] [WARNING] Errors occurred during the test execution. [TestComplete] Marking the build as UNSTABLE. [TestComplete] The test execution finished (Packnet/Packnet). Build step 'TestComplete Test' changed build result to UNSTABLE Finished: UNSTABLE ========================== I have manually launched the Jenkins agent through jnlp file and kept the console open to run my tests. Appreciate your response on this. Thanks! PhaniSolved5.1KViews0likes8CommentsRe: unable to connect to the remote instance of testcomplete (testexecute)
I got to know the problem in my system. If you have a license combination like this; TestComplete - Node-locked TestExecute - floating, 1 seat TestExecute - floating, 1 seat, 30 day trial period TestExecute - floating, 1 seat, 30 day trial period Assume the trial period ends for the test execute, then if you try to run the tests via distributed testing which kicks in all 3 VMs simultaneously then we will land up with this situation. The solution in this case would be release the test execute license after the test execution or else make the Test Complete (for test execute) service manual (under services.msc) and then kill/stop the process after test completion. Unfortunately the error message which is displayed during the execution is not proper and its confusing too. That error message is too abstract and debugging is very difficult. Hope this helps. Thanks! Phani1.4KViews1like0CommentsRe: unable to connect to the remote instance of testcomplete (testexecute)
May I know why this question of mine is not answered yet? Fyi, there is also a support ticket which I have created (Ref: Case #00444800: Distributed testing issue) since I was not getting any suggestions/solutions from this community on this issue. Kindly let me know if you need more information. Thanks!1.7KViews0likes3Commentsunable to connect to the remote instance of testcomplete (testexecute)
I am seeing the following message if I try to run the tasks synchronously. However, I am able to run individual tasks separately through job details page. The firewall is turned off in both master and slave machines, and the verification is also successful. Please find the attached file for more details. TestComplete Version: 14.50.976.7 x64 I have also tried to run the tasks through script but I got same error. Script: function Test() { var JobName = "CRUD_Operations"; var Job = NetworkSuite.Jobs.ItemByName(JobName) var Tasks = Job.Tasks var Num = Tasks.Count for (var i = 0; i < Num; i++) { //Tasks.Items(i).Run(true) Tasks.Items(i).Run(false) } } I would like to give you some more information on the set up which I am using to simulate the distributed testing; I have a node locked license (which is a server) (Version: 14.50.976.7 x64) On two VM's I have installed a trial version of TestExecute. (Version: 14.50.976.11) Appreciate your help on the same.1.8KViews1like6Comments