Contributions
Re: Unable to get the exported logs in Jenkins
I don't see a direct way to do what you want. Maybe somebody else would have a solution. Just an idea to explore: Maybe you can do it indirectly by importing the MHT file(s) into Jenkins as an artefact. If you have this file as artefact, then you can probably process it the way you want through scripts or a child Jenkins project.3KViews0likes1CommentRe: Unable to get the exported logs in Jenkins
Not sure what you mean by "exporting to wiki". You mean to HTML format? I'll attempt two solutions: - In Jenkins, you must install the TestComplete plugin, and check the "Generate MHT log file" option. - You can export a log using the options in TestExecute, but I never tried it.3KViews0likes3CommentsUnable to get the exported logs in Jenkins
Hi, The Test Complete plug-in for Jenkins export three logs by default and the MHT format is configurable. I can see all of them for a few seconds in the corresponding folder on the Jenkins agent, but they are deleted somehow after a few seconds (I can copy them and they can be opened). I tried saving them as artefacts but I have the following message in the Jenkins log: ERROR: No artifacts found that match the file pattern "*.htmlx, *.mht". Configuration error? Can the log files be moved somewhere by the plug-in? Where? Two notes: 1- I don't delete the workspace before the build starts or after. 2- I use the latest version of TestExecute on the computer that runs the Jenkins agent.Solved3.2KViews0likes6CommentsRe: Make all command line arguments configurable in Jenkins plug-in (i.e. no default arguments)
Hi, I submitted a ticket, and received an answer from the SmartBear Customer Care, which said this: Please create the corresponding feature request using the link below and our developers consider implementing it in future: https://community.smartbear.com/t5/TestComplete-Feature-Requests/idb-p/TestXCompleteFeatureRequests2.5KViews0likes0CommentsMake all command line arguments configurable in Jenkins plug-in (i.e. no default arguments)
The command line generated by the Jenkins plug-in (which is otherwise great!) has several default values, which are not the desired ones. For example, there are three /ExportLog arguments (tclogx, htmlx and txt). My tests are quite long and consequently the logs can be huge. I don't want to export them (which takes too much time); I just want to be able to display them directly in TestExecute if the test fails.2.5KViews1like6CommentsRe: HTML parsing
Hi Tanya, I have a similar problem (i.e. trying to parse a string made of HTML code), but I'm using the Desktop module of Test Complete. The two articles seem to refer to objects available only in the Web module. Can you confirm? If so, is there a way to parse HTML code using objects from the Desktop module? Note: I'm automating tests on a Java application. The HTML data I'm trying to parse is simply displayed in a pane, not a browser. Thanks!2.5KViews0likes7Comments