Fimbultyr
Contributor
Joined 8 years ago
User Profile
User Widgets
Contributions
Jenkins TestCompletePlugin failing after update to 2.4
Hi there, We are currently updating our Jenkins Server and installed the latest TestCompletePlugin with Version 2.4 Sadly the Testruns keep failing now. Our Jenkinsfile looks like this and was not changed stage("Test Job") { checkout([$class: 'GitSCM', branches: [[name: '*/master']], doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [], userRemoteConfigs: [[credentialsId: 'mylovelycreds', url: 'https://github.mylovelycompany.com/mylovelyproduct/testcomplete.git']]]) sleep time: 10, unit: 'SECONDS' testcompletetest actionOnErrors: 'MAKE_FAILED', actionOnWarnings: 'MAKE_UNSTABLE', executorType: 'TE', generateMHT: true, launchType: 'lcProject', project: 'mylovelyproduct Server', suite: 'mylovelyproduct.pjs', useTCService: true, userName: 'mylovelyfakeusername', userPassword: 'mylovelyfakepassword', timeout: '10800', useTimeout: true } In the Logs we noticed that the Parameters used for execution have changed. TestCompletePlugin 2.2 [TestComplete] The test execution started (MyLovelyProduct/MyLovelyProduct Server). [TestComplete] Found TestComplete/TestExecute installations: Type: TE, Version: 14.30.3743.11, Path: "C:\Program Files (x86)\SmartBear\TestExecute 14\x64\bin\TestExecute.exe" [TestComplete] Selected TestComplete/TestExecute installation: Type: TE, Version: 14.30.3743.11, Path: "C:\Program Files (x86)\SmartBear\TestExecute 14\x64\bin\TestExecute.exe" [TestComplete] Launching the test runner. $ '"C:\Program Files (x86)\SmartBear\TestExecute 14\bin\TestCompleteService14.exe"' //LogonAndExecute //lDomain: "" //lName: "MyLovelyProduct" //lPassword: ******** //lTimeout: "10980000" //lUseActiveSession: "true" //lCommandLine: '""C:\Program Files (x86)\SmartBear\TestExecute 14\x64\bin\TestExecute.exe" "c:\ProgramData\Jenkins\workspace\Sandbox\TestComplete Scripted Pipeline\MyLovelyProduct.pjs" /run /SilentMode /ForceConversion /ns /exit "/ExportLog:c:\ProgramData\Jenkins\workspace\Sandbox\TestComplete Scripted Pipeline\1580133532072.tclogx" "/ExportLog:c:\ProgramData\Jenkins\workspace\Sandbox\TestComplete Scripted Pipeline\1580133532072.htmlx" "/ErrorLog:c:\ProgramData\Jenkins\workspace\Sandbox\TestComplete Scripted Pipeline\1580133532072.txt" "/ExportLog:c:\ProgramData\Jenkins\workspace\Sandbox\TestComplete Scripted Pipeline\1580133532072.mht" /Timeout:10800 "/project:MyLovelyProduct Server" /DoNotShowLog /JenkinsTCPluginVersion:2.2"' [TestComplete] Test runner exit code: 2. [TestComplete] [WARNING] Error: The property checkpoint failed, because Text does not contain the substring (case-sensitive) "not important". See Details for additional information.. [TestComplete] [WARNING] Errors occurred during the test execution. [TestComplete] Marking the build as FAILED. [TestComplete] The test execution finished (MyLovelyProduct/MyLovelyProduct Server). TestCompletePlugin 2.4 [TestComplete] The test execution started (MyLovelyProduct/MyLovelyProduct Stargate). [TestComplete] Found TestComplete/TestExecute installations: Type: TE, Version: 14.30.3743.11, Path: "C:\Program Files (x86)\SmartBear\TestExecute 14\x64\bin\TestExecute.exe" [TestComplete] Selected TestComplete/TestExecute installation: Type: TE, Version: 14.30.3743.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. $ "null\SessionCreator.exe" ExecuteProcess '/c:""C:\Program Files (x86)\SmartBear\TestExecute 14\x64\bin\TestExecute.exe"" ""c:\ProgramData\Jenkins\workspace\MyLovelyProduct QA\Yoda TestComplete\MyLovelyProduct.pjs"" /run /SilentMode /ForceConversion /ns /exit ""/ExportLog:c:\ProgramData\Jenkins\workspace\MyLovelyProduct QA\Yoda TestComplete\1580394292201.tclogx"" ""/ExportLog:c:\ProgramData\Jenkins\workspace\MyLovelyProduct QA\Yoda TestComplete\1580394292201.htmlx"" ""/ErrorLog:c:\ProgramData\Jenkins\workspace\MyLovelyProduct QA\Yoda TestComplete\1580394292201.txt"" ""/ExportLog:c:\ProgramData\Jenkins\workspace\MyLovelyProduct QA\Yoda TestComplete\1580394292201.mht"" /Timeout:1800 ""/project:MyLovelyProduct Stargate"" /DoNotShowLog /JenkinsTCPluginVersion:2.4' [TestComplete] [ERROR] An exception occurred: java.io.IOException: CreateProcess error=2, The system cannot find the file specified. [TestComplete] Marking the build as FAILED. [TestComplete] [WARNING] Unable to publish test results (xml data is empty). [TestComplete] The test execution finished (MyLovelyProduct/MyLovelyProduct Stargate). Fun thing is, in TCPlugin 2.4 the Log shows a warning that we use Java Web Start, however we disconntinued using it since the new Jenkins Server does not support Javaws with OpenJDK11. You can even see, that the execution Line looks quite different now and it is using some "SessionCreate.exe" Does someone have an idea how to get the system running again? Cheers, ConstantinSolved1.7KViews0likes2CommentsRe: Does Soap ui supports swagger 3.0 or open api 3.0 importing api spec (json) file
Hi there, I got the same question/issue and figured out SoapUi is not able to import OpenAPI Files. We create Swagger UI for our Endpoints and i tried to import the swagger.json from it. Sadly both Products are from Smartbear but are not compatible. I had to chang the Header of the File to Swagger 2.0 to get the import working. Its kind of disturbing to see that Smartbear is neglecting compatibility of its own products. Cheers, Constantin6.8KViews1like0CommentsRe: TestComplete - Network Suite - Host Verification Failure
Thats really weird, since version 14 my ports changed to 6095-6097. Maybe someone from the Support Team could shed some light on this. However just stick on the Ports shown on your NetworkSuite and you should be fine. Cheers, Constantin2.5KViews1like5CommentsRe: stability problems with TestComplete
Hi there, we run a similar Test Setup i guess. I have one Master Project with 5 Subprojects + 1 Project for Distributed Testing. Overall the Performance of TestComplete seems to degrade each version and i often run into timing issues that only occur when testing with TestComplete. For example our Software starts and stops a service. With the manual Test the service needs 1-2 seconds to change state, with TestComplete doing exactly the same Steps it takes up to a Minute. Browser opening/closing is quite similar. All on the same machine of course. As i can not really fix TestComplete I often have to implement "wait for" functions or overwrite the default timeout for an object recognition. What seems to be a huge issue in distributed testing is hard disc performance. If you run into timing issues you might upgrade your machines to SSDs. Cheers, Constantin652Views0likes0CommentsRe: TestComplete - Network Suite - Host Verification Failure
Hi Chris, Yes the new Ports would be shown in the NetworkSuite Options as well. Just use the Ports shown in the NetworkSuite and you will be fine. I guess you have an older Version of TestComplete, just keep in mind that those could change after an update. Keep us updated if it works out for you. Cheers, Constantin2.5KViews0likes7CommentsRe: Test Execute freezes while Stopping Tests
I am bumping this up again. Support is trying to figure out the issue since January. Without any mentionable results, though. Maybe somebody encountered connectivity issues with distributed Testing as well? I am running my Tests against 6 machines in parallel. How are your experiences with it? Whats the highest number of machines you were able to test in the networksuite? Do you use VMs, Cloud, physical machines? Cheers, Constantin1.3KViews0likes0CommentsRe: TestComplete - Network Suite - Host Verification Failure
Hi there, I am using distributed testing via the NetworkSuite a lot and know the pain with it. First you should read the Article about the Requirements for distributed Testing. You have to follow those steps to get your client up and running propperly. You can find it here. It sounds like you did not configure your machine to allow unsecure RDP connections. Than the Ports that are documented are wrong. After Patching TC to Version 14 they changed the default Ports. They are now TCP 6095,6096,6097 If you are not sure about the Ports you can look them up in Tools -> Options... -> Engines -> Network Suite. I would first try to get RDP Connections running and make sure you can ping and connect to your Client from your Host. Than You need to configure the Firewall with the mentioned Ports. Cheers, Constantin4.3KViews2likes9CommentsRe: Test Execute freezes while Stopping Tests
Hi Tanya, Yes i think this is the only solution. I tested a few thinks like switching the connection type from RDP to Console, but i can still reproduce the issue on my machines. It looks like TC/TE runs in a Deadloop if the connection to a remote host cant be established or gets disconnected. I could reproduce this with a new Machine with Server 2019 where my Firewall Ports were not configured. I started the Networksuite, and during "Initializing" the Prozess freezes and cant be stopped. As soon as i enable the Ports, TE is able to Stop the Test. This is somehow a quite problematic behavior for a Network Test. I will keep you updated as soon as i get results from Support. Cheers, Constantin1.5KViews0likes2CommentsRe: Test Execute freezes while Stopping Tests
Hi Robert, I am running TE Version: 12.60.5545.11 Logsize is around 16-64MB. My Host Machine is Win2012R2. Client Machines are: Win 7 x64/x86 Win8.1x64/x86 Win10 x64/x86 Win2008 x86 Win2008R2 x64 Win2012 x64 Win2012R2 x64 Win2016 x64 Client Machines that fail mostly are Win7 x64, Win10 x64, Win2008 x86 I have set my Projects to Stop on Error. I can rarely reproduce the behaviour with TC while i am looking at the runstate in the networksuite. Sometimes the Machine connection seems to get lost during Synchronization <Internal> or directly when a machine runs into an error and stops the test. I even encountered issues with Synchronization Points in my Projects, with 6 Machines running in parralel the Networksuite sometimes misses 1 or 2 Machines so i had to implement Timeouts. For me it feels like the Networksuite is just unreliable and loses connection leading to a deadloop while synrchonizing or fetching results. Cheers, Constantin1.5KViews0likes4Comments