Andreas/tracks
1
0
Fork 0
mirror of https://github.com/TracksApp/tracks.git synced 2025-12-18 08:10:13 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Upgrade Selenium on Rails to r140

Browse source
This commit is contained in:
Eric Allen 2009-12-14 11:51:36 -05:00
parent 156862200b
commit 40074c71ad
117 changed files with 16789 additions and 8867 deletions
Download patch file Download diff file Expand all files Collapse all files

32
vendor/plugins/selenium-on-rails/generators/selenium/templates/rhtml.rhtml vendored
View file

@ -1,16 +1,16 @@
<p>It's often a good idea to start the test with opening <tt>/selenium/setup</tt> (see <%%= link_to 'here', :controller => 'selenium', :action => 'setup' %> for more info).</p>
<table>
<tr><th colspan="3"><%%= @page_title %></th></tr>
<tr><td>open</td><td>/selenium/setup</td><td>&nbsp;</td></tr>
<%% for page in ['/', '/home'] -%>
<tr><td>open</td><td><%%= page %></td><td>&nbsp;</td></tr>
<tr><td>assertTitle</td><td>Home</td><td>&nbsp;</td></tr>
<%% end -%>
</table>
<p>More information about the commands is available <a href="http://release.openqa.org/selenium-core/nightly/reference.html">here</a>.</p>
<p>You can write comments above and below the commands, but you can only have one set of commands, i.e. one table, per test.</p>
<p>Point the browser to <a href="<%= testcase_link %>"><%= testcase_link %></a> to see how this test is rendered, or to <a href="<%= suite_link %>"><%= suite_link %></a> to run the suite.</p>
<p>It's often a good idea to start the test with opening <tt>/selenium/setup</tt> (see <%%= link_to 'here', :controller => 'selenium', :action => 'setup' %> for more info).</p>
<table>
<tr><th colspan="3"><%%= @page_title %></th></tr>
<tr><td>open</td><td>/selenium/setup</td><td>&nbsp;</td></tr>
<%% for page in ['/', '/home'] -%>
<tr><td>open</td><td><%%= page %></td><td>&nbsp;</td></tr>
<tr><td>assertTitle</td><td>Home</td><td>&nbsp;</td></tr>
<%% end -%>
</table>
<p>More information about the commands is available <a href="http://release.openqa.org/selenium-core/nightly/reference.html">here</a>.</p>
<p>You can write comments above and below the commands, but you can only have one set of commands, i.e. one table, per test.</p>
<p>Point the browser to <a href="<%= testcase_link %>"><%= testcase_link %></a> to see how this test is rendered, or to <a href="<%= suite_link %>"><%= suite_link %></a> to run the suite.</p>

28
vendor/plugins/selenium-on-rails/generators/selenium/templates/rselenese.rhtml vendored
View file

@ -1,14 +1,14 @@
# It's often a good idea to start the test with 'setup'.
# See /selenium/setup for more info.
setup
open '/'
assert_title 'Home'
# More information about the commands is available at:
# http://release.openqa.org/selenium-core/nightly/reference.html
# See also the RDoc for SeleniumOnRails::TestBuilder.
#
# Point the browser to <%= testcase_link %> to see
# how this test is rendered, or to <%= suite_link %> to
# run the suite.
# It's often a good idea to start the test with 'setup'.
# See /selenium/setup for more info.
setup
open '/'
assert_title 'Home'
# More information about the commands is available at:
# http://release.openqa.org/selenium-core/nightly/reference.html
# See also the RDoc for SeleniumOnRails::TestBuilder.
#
# Point the browser to <%= testcase_link %> to see
# how this test is rendered, or to <%= suite_link %> to
# run the suite.

22
vendor/plugins/selenium-on-rails/generators/selenium/templates/selenese.rhtml vendored
View file

@ -1,11 +1,11 @@
It's often a good idea to start the test with opening <tt>/selenium/setup</tt> (see "here":/selenium/setup for more info).
|open|/selenium/setup|
|open|/|
|assertTitle|Home|
More information about the commands is available "here":http://release.openqa.org/selenium-core/nightly/reference.html.
You can write comments above and below the commands, but you can only have one set of commands, i.e. one table, per test. "RedCloth":http://www.whytheluckystiff.net/ruby/redcloth/ is used for formatting if installed.
Point the browser to "<%= testcase_link %>":<%= testcase_link %> to see how this test is rendered, or to "<%= suite_link %>":<%= suite_link %> to run the suite.
It's often a good idea to start the test with opening <tt>/selenium/setup</tt> (see "here":/selenium/setup for more info).
|open|/selenium/setup|
|open|/|
|assertTitle|Home|
More information about the commands is available "here":http://release.openqa.org/selenium-core/nightly/reference.html.
You can write comments above and below the commands, but you can only have one set of commands, i.e. one table, per test. "RedCloth":http://www.whytheluckystiff.net/ruby/redcloth/ is used for formatting if installed.
Point the browser to "<%= testcase_link %>":<%= testcase_link %> to see how this test is rendered, or to "<%= suite_link %>":<%= suite_link %> to run the suite.