Felixg
Occasional Contributor
Joined 7 years ago
User Profile
User Widgets
Contributions
Re: Log.SaveResultsAs() do not work for the LogFormat lsJUnit
Ok even if the Log.SaveResultsAs() function does not work with lsJUnit LogFormat, due to you last answer I found the way to use the command line argument /ExportSummary through the TestComplete Jenkins pluggin. Indeed, there were several tricky points. So when you go to the plugin configuration in your job, you click on "settings", and in the command line arguments you put : "/ExportSummary:${WORKSPACE}\results.xml" The tricky points are : Even if the Jenkins server, and the slave agent, run on a Windows machine, use the UNIX syntax ${WORKSPACE} and not %WORKSPACE% (even if you use "\" and not "/" as path delimiter ... so UNIX syntax for environment variables, Windows syntax for others) The quotes should include the argument also : "/ExportSummary:${WORKSPACE}\results.xml" and not /ExportSummary:"${WORKSPACE}\results.xml" Then you can specified in the post build step to publish JUnit report giving the following path : results.xml Thanks all for your answers1.9KViews2likes0CommentsRe: Log.SaveResultsAs() do not work for the LogFormat lsJUnit
Hi hkim5 , I have tried Log.SaveResultsAs(Project.ConfigPath + "\\MHT_Files\\" + "results.xml", lsJUnit) And it does not work. The folder MHT_Files is well created into the project path, but it is empty. I have well read the documentation, and I want to export the Project Suite logs, so I use the default value "lesFull", and I run the PJS. I have tried using and not using the optional arguments, with True False for the ExportVisualizerImages argument, etc ... It never works. Moreover, this solution can not solve our issur, because, as I said in my first message, we have to get a known path because using environment variables in command line is not working, and the path to the summary to publish in the Jenkins job configuration is relative to workspace path1.9KViews0likes1CommentRe: Log.SaveResultsAs() do not work for the LogFormat lsJUnit
Hi hkim5 , Ihave tried what you suggested, I replaced lsJUnit by 5 and lesFull by 0, I tried with True and False (I forgot to precise in my first message that we are in Python) for the third parameter, and any summary report is generated.2KViews0likes3CommentsLog.SaveResultsAs() do not work for the LogFormat lsJUnit
Hi everyone, I would like to export JUnit report to see my summary reports in Jenkins. Of course I read the Log.SaveResultsAs() function documentation, Viewing TestComplete Test Results in Jenkins and also Exporting Test Results , and the related documentations. I want to export my test summary from my scripts using Log.SaveResultsAs("C:\\Temporary jenkins workspace with spaces\\exports\\results.xml", lsJUnit, True, lesFull) But it always returns "False", and the summary report is not exported. However, I am not doing something very complicated, and I have just called a function as it is given in the documentation as an example. I also export logs with "lsZip" and "lsPackedHTML log formats with the same call, just adjusting the file name (and extension of course), and in that cases it works correctly. Can you confirm if it is realy a bug of the Log.SaveResultsAs() function or if there are some specific things to do that are not written in the documentation please ? PS: Why do I not use the /ExportSummary command line argument ? Because when you configure a Jenkins job to publish JUnit report you have to give a relative path to the workspace. Whereas the /ExportSummary argument expects an absolute path, the Jenkins workspace depends on the job name, so we can not use the command line argument because it is to heavy to edit the command line argument value each time we edit the job name (we use the job name as a test run title, so we edit it sometimes). Moreover we have one job per PJS, deployed from a job template, so the commande line argument value has to be set for each job. And in the /ExportSummary command line argument value we can not use environment variables, like the %WORKSPACE% variable which holds the running Jenkins.SolvedRe: Is a testComplete chronium integration planned for next versions ?
Hi everyone, So I have just got an answer from the support team, and this answer is : Edge based on Chromium won't be supported in TestComplete 14.40. Probably, it'll be supported in the next version of the tool, but there are no exact plans or ETA. Thanks eeryone to have followed and replied to my topic ! Regards, Felix2.1KViews2likes1CommentRe: Is a testComplete chronium integration planned for next versions ?
Hi sonya_m , of course, as I said in my first answer to Marsha_R , it is my intention. At the moment, the support team has just answer me they are consulting the development team and they keep me informed. I will keep this topic opened and share the answer when I'll got it2.1KViews1like2CommentsRe: Is a testComplete chronium integration planned for next versions ?
Thank you AlexKaras , I followed the link you gave, unfortunately one answer is the solution of the third link I gave in my first message, and it does not work for us, and even if it works, we have to do specific development, which is our issue. And another answer is to reinstall an earlier version of Windows 10 to get the previous version of Edge, which not our aim.2.1KViews0likes6CommentsIs a testComplete chronium integration planned for next versions ?
Hi everyone, We develop automated tests in TestComplete for a Web application. We are using TestComplete 14.30. Our scripts take the browser name as input parameter (we pass this parameter to the Sys.Browser() object), then we configure 4 test items, one per browser in Firefox, Chrome, Edge, Internet Explorer, and we run our test on 4 web browsers with exactly the same script ! Now we have a problem since Microsoft released his new Edge based on Chromium. of course, we read these documentations About Support for Chromium Embedded Framework , Preparing CEF-Based Applications for Testing , AccessToChromiumContent Property (the example given in that 3rd link does not work for us), but it suggests to use TestedApps instead of Sys.Browser() object, which is completely a different approach, and so we have to develop some specific code specificaly for Edge. Since a Smartbear TestComplete integration pluggin is available on Chrome, and allows us to interact with a Web application in the Chrome browser with Sys.Browser() object, such a plugin is planned to be developped ? Or another integration way ? We need to know if we have to develop that specific code, or if we have just to wait and disable our test items running on Edge just a moment, waiting for that integration. Thanks for reading, regards, FelixSolved2.4KViews3likes10CommentsRe: When trying Click Action I get message Permission denied to access property in web testing on Firefo
Additional information : after many experimentations with SmartBear Support Team, we find out that TestComplete 12.60 solves this issue, but only if you set the Firefox property browser.tabs.remote.autostart to true (enter about:config in URL address bar to reach the configuration menu). Be careful, currently the documentation is still not up to date, and moreover, it works only with TC 12.60, not with earlier versions. Hope it can help someone !3KViews2likes0Comments