TestComplete Support Plugin Compatibility Issue
Environment. - TestComplete Support Jenkins Plugin version: 2.10 - Jenkins version: 2.555.1 - Java version: 21.0.7 This are Console logs generated once the build is completed. [TestComplete] Test runner exit code: 0. [TestComplete] [WARNING] Unable to publish test results (xml data is empty) The TestComplete plugin throws a ClassNotFoundException for javax.xml.bind.DatatypeConverter when running on Java 21. This causes all TestComplete jobs to fail. java.lang.ClassNotFoundException: javax.xml.bind.DatatypeConverter at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:445) Caused: java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter at PluginClassLoader for TestComplete//com.smartbear.jenkins.plugins.testcomplete.parser.LogNodeUtils.startTimeToTimestamp(LogNodeUtils.java:425) at PluginClassLoader for TestComplete//com.smartbear.jenkins.plugins.testcomplete.parser.LogParser2.convertSummaryToXML(LogParser2.java:216) at PluginClassLoader for TestComplete//com.smartbear.jenkins.plugins.testcomplete.parser.LogParser2.parse(LogParser2.java:278) In the attached screen we are unable to view Graph and Test complete test results as previously.
TC Plugin 2.10 on Java 21 ClassNotFoundException:javax.xml.bind.DatatypeConverter blocks result pub
TestComplete Jenkins Plugin 2.10 on Java 21 — ClassNotFoundException: javax.xml.bind.DatatypeConverter blocks all result publishing Environment: - TestComplete Jenkins Plugin: 2.10 - Jenkins: 2.555.2 - Agent Java: Eclipse Temurin 21.0.11 (JNLP inbound agent) - Controller Java: 21.0.5 - TestExecute: 15.82.62.11 / TestComplete: 15.83.1.7 (both updated to latest, no change in behavior) Issue: Confirming the same issue already reported in this thread and in the related idea (community.smartbear.com/idea/.../280452). Plugin incompatible with Java 21 - ClassNotFoundException: javax.xml.bind.DatatypeConverter | SmartBear Community and TestComplete Support Plugin Compatibility Issue | SmartBear Community The TestComplete/TestExecute test run completes successfully — exit code 0, and I personally watched the run finish correctly on the node — but the Jenkins build still fails at the results-publishing stage with: [TestComplete] [WARNING] Unable to publish test results (xml data is empty). FATAL: javax/xml/bind/DatatypeConverter java.lang.ClassNotFoundException: javax.xml.bind.DatatypeConverter Caused: java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter at PluginClassLoader for TestComplete//com.smartbear.jenkins.plugins.testcomplete.parser.LogNodeUtils.startTimeToTimestamp(LogNodeUtils.java:425) at PluginClassLoader for TestComplete//com.smartbear.jenkins.plugins.testcomplete.parser.LogParser2.convertSummaryToXML(LogParser2.java:216) at PluginClassLoader for TestComplete//com.smartbear.jenkins.plugins.testcomplete.parser.LogParser2.parse(LogParser2.java:278) at PluginClassLoader for TestComplete//com.smartbear.jenkins.plugins.testcomplete.TcTestBuilder.processFiles(TcTestBuilder.java:1108) This is 100% reproducible on every build regardless of test content, confirming the root cause is the plugin's log-to-XML summary step (LogNodeUtils.startTimeToTimestamp) calling a JAXB class that was removed from the JDK itself starting with Java 11 (JEP 320). Already ruled out: - Not a TestComplete/TestExecute version issue — updated both to latest 15.82.x, same result. - Not fixable via the job-level "JDK" tool selection — that only sets PATH/JAVA_HOME for build steps, it doesn't change the JVM already running the Jenkins process. - Not fixable by running on Java 17 instead — javax.xml.bind was already removed as of Java 11, so 17 has the same problem; and in any case Jenkins 2.555.x requires Java 21 or 25 on both controller and agent JVMs, so downgrading isn't an option for us. Jenkins Console log: [TestComplete] The test execution started (LMS/LMS). [TestComplete] Found TestComplete/TestExecute installations: Type: TE, Version: 15.82.62.11, Path: "C:\Program Files (x86)\SmartBear\TestExecute 15\x64\bin\TestExecute.exe" Type: TELite, Version: 15.82.62.50, Path: "C:\Program Files (x86)\SmartBear\TestExecuteLite 15\x64\bin\TestExecuteLite.exe" [TestComplete] Selected TestComplete/TestExecute installation: Type: TE, Version: 15.82.62.11, Path: "C:\Program Files (x86)\SmartBear\TestExecute 15\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 15\x64\bin\SessionCreator.exe"' ExecuteProcess '/c:""C:\Program Files (x86)\SmartBear\TestExecute 15\x64\bin\TestExecute.exe"" "C:\JenkinsAgent\workspace\Production\RegressTest\LMS\LMS_RegressTest01\LMS.pjs" /run /accesskey:******** /SilentMode /ForceConversion /ns /exit "/ExportLog:C:\JenkinsAgent\workspace\Production\RegressTest\LMS\LMS_RegressTest01\1783430886140.tclogx" "/ExportLog:C:\JenkinsAgent\workspace\Production\RegressTest\LMS\LMS_RegressTest01\1783430886140.htmlx" "/ErrorLog:C:\JenkinsAgent\workspace\Production\RegressTest\LMS\LMS_RegressTest01\1783430886140.txt" "/ExportLog:C:\JenkinsAgent\workspace\Production\RegressTest\LMS\LMS_RegressTest01\1783430886140.mht" "/project:LMS" /DoNotShowLog /JenkinsTCPluginVersion:2.10' [TestComplete] Test runner exit code: 0. [TestComplete] [WARNING] Unable to publish test results (xml data is empty). FATAL: javax/xml/bind/DatatypeConverter java.lang.ClassNotFoundException: javax.xml.bind.DatatypeConverter Caused: java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter at PluginClassLoader for TestComplete//com.smartbear.jenkins.plugins.testcomplete.parser.LogNodeUtils.startTimeToTimestamp(LogNodeUtils.java:425) at PluginClassLoader for TestComplete//com.smartbear.jenkins.plugins.testcomplete.parser.LogParser2.convertSummaryToXML(LogParser2.java:216) at PluginClassLoader for TestComplete//com.smartbear.jenkins.plugins.testcomplete.parser.LogParser2.parse(LogParser2.java:278) at PluginClassLoader for TestComplete//com.smartbear.jenkins.plugins.testcomplete.TcTestBuilder.processFiles(TcTestBuilder.java:1108) at PluginClassLoader for TestComplete//com.smartbear.jenkins.plugins.testcomplete.TcTestBuilder.performInternal(TcTestBuilder.java:799) at PluginClassLoader for TestComplete//com.smartbear.jenkins.plugins.testcomplete.TcTestBuilder.perform(TcTestBuilder.java:568) at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:79) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:817) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:164) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:526) at hudson.model.Run.execute(Run.java:1842) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:44) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:456) Questions: 1. Is there an ETA for an official plugin fix that removes the JAXB dependency? 2. Is there a supported interim workaround? 3. Can SmartBear confirm/validate the community patch posted by siho in this thread (replacing DatatypeConverter with java.time) as safe for production use? Happy to share the full console log or additional screenshots on request.results are not visible when clicking on show in explorer for each log
I executed a test case but when i click on 'Sow in explorer' fresult folder doesnt cntain .html files for both detail and summary logs. but when i export it to a folder it has both of them please help me how to fix this for html files.. iwant the result to be viewed as html also please help me with the testcript in python onhow i can use it to save results aftre each executionDark Mode for .mht files?
(If what I want is already there, then please accept my apologies and pretty-please tell me how to configure it...) I can view log files within TC in dark mode by setting dark mode in TC itself. When saving logs as .mht files, however, they are only saved in light mode. Furthermore, people have different preferences (dark vs. light). There is currently a W3C standard in which websites can ask the user's browser whether it's configured for light or dark mode, so that the server can adjust CSS accordingly. Edge knows how to respond to this query. What I'd like to see is this mechanism embedded in the .mht file so that the log will display as light or dark according to my Edge settings. A Google search for 'support for dark mode in mhtml files' gives an AI answer claiming that it's possible. (Or course, it's AI, so...)
Enabling Screenshots on every event
Hello, How can i turn on screenshoting every event? right now it only screens when there is error. not just some events. besides when i double click event it does not redirect me to the exact line of code where event has happend. error does. my testcomplete version is 15.74.33.7. i am making desktop script tests. let me now if you need any kind of information
Test Complete Report Summary of Execution
Hello ! So right now we are getting our report summaries in .htm form. I have my test cases setup in "Groups" which explains what is being tested inside of this group. So my question is, is it possible to show those groups in the summary report so its easier to read where things went wrong on what "test case"?
Saving Logs as part of Azure Devops pipeline
Hello there We have a Test Complete project suite which runs an execution plan in a test project. At the end of the execution plan, we generate a HTML log for the test run, which shows the results of all the steps in the execution plan. This works fine in TestComplete and generates a HTML report with all the steps included. I am now trying to run this project suite via a pipeline in Azure Devops server. I have managed to get the pipeline up and running, but when it runs via the pipeline it only generates a log for the last step in the execution plan (i.e. the SavedLogs step). I assume that the test runner is running all the test cases as separate processes, so it is generating individual logs for each test case. Is there any way to get the pipeline to run all the tests in the project suite together, so that a complete HTML log for the run can be produced?
Process "crashed" and test fails when closing the application in test
Hi all, We use TestComplete 15 to perform regression testing on our Delphi desktop application. We have a simple test: open the application short wait follows close the application Testcomplete will fail the test stating the "TestApp.exe" process crashed and test execution is interrupted. Closing the application via X or through the 'Main Menu - Exit' results in the same error. The Sys.WaitProcess method also didn't help. We have also attempted to close it using the .Close() method. Maybe I'm placing the Sys.WaitProcess method in the wrong spot. I would be very grateful for a code snippet (JavaScript) and any help. thx.Generate a segregated report identifying error as script failure or an application issue
Hi Team, Problem Statement : How can you identify whether an error is a script failure or an application issue through logs, and generate a segregated report at the end of the test execution? ======================================================================== Here, I'm trying to understand if anyone has tried to create a framework (or has already developed and is using one) in such a way that, once the test execution completes, we will have logs attached to the test execution report. I want to go even deeper and segregate failures (if any) based on script and application issues. I understand that until we analyze, the failures cannot be easily segregated. But there could be some errors that can be clearly identified as script errors rather than application issues. Does TestComplete provide anything to identify such errors? If yes, what are those? What am I aiming at? -- To reduce the analysis time (so the report can be shared earlier) as not all the errors from logs need to be given the same priority. Thank you in advance for your thoughts and inputs.
