You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Don Brown (JIRA)" <ji...@apache.org> on 2008/06/13 02:32:05 UTC

[jira] Updated: (WW-1912) Selenium Tests for Showcase

     [ https://issues.apache.org/struts/browse/WW-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Don Brown updated WW-1912:
--------------------------

    Fix Version/s:     (was: 2.1.x)
                   2.2.x

> Selenium Tests for Showcase
> ---------------------------
>
>                 Key: WW-1912
>                 URL: https://issues.apache.org/struts/browse/WW-1912
>             Project: Struts 2
>          Issue Type: New Feature
>          Components: Unit Tests
>    Affects Versions: 2.0.6
>            Reporter: Martin Gilday
>             Fix For: 2.2.x
>
>         Attachments: mgilday-selenium.txt
>
>
> I have begun creating some Selenium tests for the Struts 2 Showcase.
> So far the changes cover:
> * Updating the showcase POM with a Selenium profile
> * Updated the showcase POM to use the latest version of Jetty (6.1.3)
> * A Selenium test for creating a Skill
> * A Selenium test for editng a Skill
> This is works in the same manner as described in the Shale docs http://shale.apache.org/shale-apps/selenium.html
> Currently you must run with mvn -Pselenium clean jetty:run-exploded and then visit http://127.0.0.1:8080/struts2-showcase/selenium/core/TestRunner.html
> A plain jetty:run will not work as the Selenium tests are not in the default web root.  An alternative is to package and deploy with Cargo
> If someone could try this out and give some feeback on if they think it is a reasonable approach then I can continue creating the rest of the test suite.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.