You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Martin Gilday (JIRA)" <ji...@apache.org> on 2007/05/07 00:40:42 UTC
[jira] Created: (WW-1912) Selenium Tests for Showcase
Selenium Tests for Showcase
---------------------------
Key: WW-1912
URL: https://issues.apache.org/struts/browse/WW-1912
Project: Struts 2
Issue Type: New Feature
Components: Tests
Affects Versions: 2.1.0
Reporter: Martin Gilday
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.
[jira] Updated: (WW-1912) Selenium Tests for Showcase
Posted by "Martin Gilday (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Gilday updated WW-1912:
------------------------------
Attachment: mgilday-selenium.txt
> Selenium Tests for Showcase
> ---------------------------
>
> Key: WW-1912
> URL: https://issues.apache.org/struts/browse/WW-1912
> Project: Struts 2
> Issue Type: New Feature
> Components: Tests
> Affects Versions: 2.1.0
> Reporter: Martin Gilday
> 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.
[jira] Updated: (WW-1912) Selenium Tests for Showcase
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ 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.1)
2.1.x
As I said, I'd really like to see this added, but it looks like it'll need a bit more work. If the tests can run as part of our automated build, that would be idea.
> 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.1.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.
[jira] Updated: (WW-1912) Selenium Tests for Showcase
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (WW-1912) Selenium Tests for Showcase
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Don Brown updated WW-1912:
--------------------------
Affects Version/s: (was: 2.1.0)
2.0.6
Fix Version/s: 2.1.0
Very cool, I'm putting against 2.1.0 in hopes that another Selenium user can help out.
> Selenium Tests for Showcase
> ---------------------------
>
> Key: WW-1912
> URL: https://issues.apache.org/struts/browse/WW-1912
> Project: Struts 2
> Issue Type: New Feature
> Components: Tests
> Affects Versions: 2.0.6
> Reporter: Martin Gilday
> Fix For: 2.1.0
>
> 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.