|
This plugin publishes the reports generated by the Canoo WebTest tool for each build. DescriptionThis plugin simply publishes the reports generated by the Canoo WebTest tool http://webtest.canoo.com. It is assumed that the webtests are run during the build process. If the build succeeds, this plugin will then create a link to the Webtests from the build page. ConfigurationConfiguration is rather straightforward: simply indicate where the Webtest results are placed by your build process: ![]() When a build has successfully run and the Webtest results have been generated, the plugin will create a link to the Webtest results in the build results page: ![]() Clicking on the "Webtest Results" link will take you to the standard Canoo WebTests report pages. NotesIf you wish to integrate the Webtest results into the standard "Test Result" charting, you will need to use Webtest version R_1657 or newer, which produces an overview report in junit-report format (WebTestOverview.junit.xml) that the junit report publisher can parse. However, this report currently only contains information on whether tests passed or failed, and how long the tests took. Therefore, this method is most useful in tracking test pass/fail trends, and can be useful when used in conjunction with the webtestpresenter plugin. Version HistoryVersion 0.21 Mar 16 2008
Version 0.22 Jul 14 2008
|



Comments (2)
May 09, 2008
Tom Larrow says:
This plugin has been very helpful for us, however I have noticed a few oddities....This plugin has been very helpful for us, however I have noticed a few oddities.
Since installing this plugin, the Webtest result is now considered an "Build Artifact" and included in the build artifact screen. Before this simply showed our .ear file that had been deployed. Now we have to drill down through the file structure to find the .ear. or choose to download the zip file that contains both the .ear and the webtest. It would be great if the webtest did not show up as an artifact.
Secondly if a build fails, the option to view the webtest is not available. The only way to view it is to drill down through the workspace, and view the actual webtest .html file. This causes a problem especially when it is the webtest fails, and that causes the build to fail. When this happens the next build causes the workspace to be re-built, and you have lost the old webtest results. You're left with a build that failed, and no webtests that show WHY it failed.
Sep 18
Adam Ambrose says:
Issue 2067 https://hudson.dev.java.net/issues/showbug.cgi?id=2067 should cover t...Issue 2067 should cover these problems, and version 0.22 was meant to fix them.