Webtest Plugin issues

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Webtest Plugin issues

Tom Larrow
Hello,

I'm having a few issues with the Canoo Webtest Presenter Plugin.  The issues seem to stem from the way that the plugin treats the Webtests results as an artifact.

First off, since adding webtests to the project, Hudson now lists the results directory as a "Build Artifact"  Where before that just listed the .ear, or the .jar that was built, now it displays a directory structure, which contains both that file, and the webtests.  The ability to just download the one file is gone, replaced with an option to download a .zip file containing both the .jar file, and the webtest results.  For instance, the Violations plugin does not consider the .xml for checkstyle or findbugs to be artifacts, the Webtest plugin should treat the webtest results the same way.

Secondly because the Plugin treats the webtests results as an artifact, and Hudson doesn't publish artifacts of failed builds, if a build fails, there is nothing reported by the webtest plugin.  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.

-Tom Larrow
Reply | Threaded
Open this post in threaded view
|

RE: Webtest Plugin issues

ruel loehr

I think we need a subcomponent for the webtest plugin added to the issue tracker.

 

 


From: Tom Larrow [mailto:[hidden email]]
Sent: Monday, July 07, 2008 12:43 PM
To: [hidden email]
Subject: Webtest Plugin issues

 

Hello,

I'm having a few issues with the Canoo Webtest Presenter Plugin.  The issues seem to stem from the way that the plugin treats the Webtests results as an artifact.

First off, since adding webtests to the project, Hudson now lists the results directory as a "Build Artifact"  Where before that just listed the .ear, or the .jar that was built, now it displays a directory structure, which contains both that file, and the webtests.  The ability to just download the one file is gone, replaced with an option to download a .zip file containing both the .jar file, and the webtest results.  For instance, the Violations plugin does not consider the .xml for checkstyle or findbugs to be artifacts, the Webtest plugin should treat the webtest results the same way.

Secondly because the Plugin treats the webtests results as an artifact, and Hudson doesn't publish artifacts of failed builds, if a build fails, there is nothing reported by the webtest plugin.  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.

-Tom Larrow

Reply | Threaded
Open this post in threaded view
|

Re: Webtest Plugin issues

Kohsuke Kawaguchi
Administrator
Loehr, Ruel wrote:
> I think we need a subcomponent for the webtest plugin added to the issue tracker.

Added 'webtest-plugin'

>
>
> ________________________________
> From: Tom Larrow [mailto:[hidden email]]
> Sent: Monday, July 07, 2008 12:43 PM
> To: [hidden email]
> Subject: Webtest Plugin issues
>
> Hello,
>
> I'm having a few issues with the Canoo Webtest Presenter Plugin.  The issues seem to stem from the way that the plugin treats the Webtests results as an artifact.
>
> First off, since adding webtests to the project, Hudson now lists the results directory as a "Build Artifact"  Where before that just listed the .ear, or the .jar that was built, now it displays a directory structure, which contains both that file, and the webtests.  The ability to just download the one file is gone, replaced with an option to download a .zip file containing both the .jar file, and the webtest results.  For instance, the Violations plugin does not consider the .xml for checkstyle or findbugs to be artifacts, the Webtest plugin should treat the webtest results the same way.
>
> Secondly because the Plugin treats the webtests results as an artifact, and Hudson doesn't publish artifacts of failed builds, if a build fails, there is nothing reported by the webtest plugin.  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.
>
> -Tom Larrow
>

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment