cancel
Showing results for 
Search instead for 
Did you mean: 

Jenkins test failure on test execute 14.40.1658.11

SOLVED
Highlighted
New Contributor

Jenkins test failure on test execute 14.40.1658.11

Hello,
Since the installation of Test Execute 14.40.1658.11 I can no longer launch tests via Jenkins.
I have the following log message : 

 

 

[TestComplete] The test execution started (mhp-tests-gui/mhp-tests-gui/AUTO_PE_000997_932/AUTO_PE_000997_932).
[TestComplete] Found TestComplete/TestExecute installations:
	Type: TE, Version: 12.60.5545.11, Path: "C:\Program Files (x86)\SmartBear\TestExecute 12\bin\TestExecute.exe"
	Type: TE, Version: 14.40.1658.11, Path: "C:\Program Files (x86)\SmartBear\TestExecute 14\x64\bin\TestExecute.exe"
[TestComplete] Selected TestComplete/TestExecute installation:
	Type: TE, Version: 14.40.1658.11, Path: "C:\Program Files (x86)\SmartBear\TestExecute 14\x64\bin\TestExecute.exe"
[TestComplete] Launching the test runner.
$ "null\SessionCreator.exe" ExecuteProcess '/c:""C:\Program Files (x86)\SmartBear\TestExecute 14\x64\bin\TestExecute.exe"" "C:\Jenkins\workspace\STAGO\Lancement_Test_Unitaire_PCFixe\mhp-tests-gui\mhp-tests-gui\mhp-tests-gui.pjs" /run /SilentMode /ForceConversion /ns /exit "/ExportLog:C:\Jenkins\workspace\STAGO\Lancement_Test_Unitaire_PCFixe\1592322644023.tclogx" "/ExportLog:C:\Jenkins\workspace\STAGO\Lancement_Test_Unitaire_PCFixe\1592322644023.htmlx" "/ErrorLog:C:\Jenkins\workspace\STAGO\Lancement_Test_Unitaire_PCFixe\1592322644023.txt" "/ExportLog:C:\Jenkins\workspace\STAGO\Lancement_Test_Unitaire_PCFixe\1592322644023.mht" "/project:mhp-tests-gui" "/unit:AUTO_PE_000997_932" "/routine:AUTO_PE_000997_932" /DoNotShowLog /JenkinsTCPluginVersion:2.4'
[TestComplete] [ERROR] An exception occurred:
java.io.IOException: CreateProcess error=2, Le fichier spécifié est introuvable.
[TestComplete] Marking the build as FAILED.
[TestComplete] [WARNING] Unable to publish test results (xml data is empty).
[TestComplete] The test execution finished (mhp-tests-gui/mhp-tests-gui/AUTO_PE_000997_932/AUTO_PE_000997_932).
Build step 'TestComplete Test' changed build result to FAILURE
Finished: FAILURE

 

Can you help me please ?
it's pretty urgent ! thank you in advance

cordially Salim

 

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
New Contributor

Re: Jenkins test failure on test execute 14.40.1658.11

You can close the subject, I managed to solve the problem by downloading the latest version of the 2.4.1 plug-in and forcing TestExecute to run with the 32-bit version, everything is back to normal
 
 
 

View solution in original post

5 REPLIES 5
Highlighted
Community Manager

Re: Jenkins test failure on test execute 14.40.1658.11

Let's get help from the Community!

 

@Marsha_R @BenoitB @tristaanogre @cunderw @AlexKaras 

Your suggestions?🙂


Sonya Mihaljova
Community and Education Specialist

Did my reply answer your question? Give Kudos or Accept it as a Solution to help others. ⬇️⬇️⬇️
Highlighted
Community Leader

Re: Jenkins test failure on test execute 14.40.1658.11

"null\SessionCreator.exe"

 

Look like the path is not set. Check that. Shouldn't have null but the path of sessioncreator here.

 

 

 

Un sourire et ça repart

Highlighted
New Contributor

Re: Jenkins test failure on test execute 14.40.1658.11

Where can i set the path of Session Creator ? I want to clarify that before downloading the version 14 of Test Execute, I did not have this problem and no line which refers to SessionCreator

 

I saw on another discussion that it was related to the 2.4 plugin because the person had the same logs as me, can someone confirm me and if so, how to solve the problem? 

 

here is the discussion link : https://community.smartbear.com/t5/TestComplete-General-Discussions/Jenkins-TestCompletePlugin-faili...   

 

Thank you 

 

Highlighted
New Contributor

Re: Jenkins test failure on test execute 14.40.1658.11

@sonya_m   

Can someone please help me? I am blocked by this situation ! 
 
 
 
 
Highlighted
New Contributor

Re: Jenkins test failure on test execute 14.40.1658.11

You can close the subject, I managed to solve the problem by downloading the latest version of the 2.4.1 plug-in and forcing TestExecute to run with the 32-bit version, everything is back to normal
 
 
 

View solution in original post

New Here?
Join us and watch the welcome video:
Announcements
Top Kudoed Authors