IFERNANDEZ
Occasional Contributor
Joined 8 years ago
User Profile
User Widgets
Contributions
TC/ TE integration with Testlink successful
Hi. Last few weeks I've been fighting against the strange case of how Smartbear did not provide a clear guide lines on how to integrate TC/TE with the most used open source Test management tool: Testlink and Jenkins. All chats I've found here in the community and around were not clear on how to. Moreover, SmartBear says that the best way to integrate TC/TE with Testlink is forget Testlink and buy QAComplete. In my opinion, not very professional answer from their side, when by example my company has paid a huge amount for TC/TE. So a good support should have been provided. This is my complaning part. I've missed kind of help to the customers that like my company have bet for this test tool. Now, I will try to help all those that are willing to integrate Jenkins, TE/TC and Testlink: - Testcomplete plugin works fine, you only need to activate the Junit results flag of the plugin. - The problems come now: You must use the Jenkins API to get the results in xml format. As TC/TE cannot run in a Linux machine, you must install Powershell in your Windows machine, in order to get the results of your job and save them as *.xml file. Results of your job can be found in **/testReport/api/xml CAUTION!! This results are not JUNIT format!! But in pseudo-JUNIT style! Testlink plugin cannot read this format, that is why no matter the hard you try... your plugin config is ok... the problem is the format of your results... Many people say they configure correctly the plugin settings, and have a huge trouble after it, because, they see 'Not run' in their tests.... The solution is to parse the results to real Junit format. My recommendation is to create an easy *.xsl script and use the msxsl processor of Microsoft by example. Once you have it, if the config of your Testlink plugin is ok, the result seeking strategy will work, and your test results will be updated in the Testlink. For further questions do not hesitate in asking me. BR1KViews0likes2CommentsTestlink integration with TC/TE junit results format and Jenkins
Hi all. I'm currently facing the necessity of publishing my TC/TE results in Testlink using Jenkins. In doing so, Testlink must read a results report in next formats: Junit, TestNG or TAP. If you use the API provided by Jenkins you find in an url **/api/xml a Junit-style report, WHICH is a PSEUDO-JUNIT, but is not Junit. This makes the Testlink plugin to read your tests, but not the results of them, becasue, as mentioned above, it is not Junit 100%. Besides, this can be check when you try to use the plugin Publish Junit test result report. It cannot identify your results, because is not Junit 100%. Has anyone got the chance of solving this? The workaround is using Process xUnit test result report to parse to Junit. Then you can choose the TestComplete 11x-12x or 9x-10x. In doing so, you need the *.mht result doc file. But my Jenkins job is removing it after finishing the execution... Has anyone been able to get the mht result after executing in Jenkins? Many thanks in adavnce1.3KViews0likes2CommentsRe: Need actual Junit reports to be generated and not Just Junit Style reports
Hi. I'm stuck exactly at the same point. You're getting the actual /api/xml results produced by Jenkins. But they're not Junit - style. So you need to parse them. Which actually is not that simple. Unfortunately. This affects result publishing, Testlink... A real disaster from Smartbear / Testcomplete integration with Jenkins.4KViews0likes0CommentsTest record processing takes so much
After stopping recording our KW tests it takes Testcomplete many time to process it. It can be only one click in an object of website. This is slowing down our test recording and automation. Is it normal? Does it depend on something? My PC is a Dell with a Intel i7 processor and 8GB RAM. There are not any other time-consuming running at the same time in my computer. version of TC is 12.42.30.48.7 Please we are stuck on this, if someone can help us, would be perfect. Thanks and BR892Views0likes1CommentStop on error
My question here is that we have a test suite with different projects inside (well, becasue this is TC way of organization) and inside those projects KW tests. Then, if you check stop on error at suite level, how affects projects, and at project level, how affects KWords? My guess is obvious for project level, but not for suite level as it can only be one suite. thanks in advance1KViews0likes3Comments