Sha256: 7dbf82322034893646c2aaf514606fde8781264a9437991829eb00e08c5e39c6
Contents?: true
Size: 1.69 KB
Versions: 7
Compression:
Stored size: 1.69 KB
Contents
Feature: Manage authentications
In order to [goal]
[stakeholder]
wants [behaviour]
Scenario: Register new authentication
Given I am on the new authentication page
And I press "Create"
# Rails generates Delete links that use Javascript to pop up a confirmation
# dialog and then do a HTTP POST request (emulated DELETE request).
#
# Capybara must use Culerity/Celerity or Selenium2 (webdriver) when pages rely
# on Javascript events. Only Culerity/Celerity supports clicking on confirmation
# dialogs.
#
# Since Culerity/Celerity and Selenium2 has some overhead, Cucumber-Rails will
# detect the presence of Javascript behind Delete links and issue a DELETE request
# instead of a GET request.
#
# You can turn this emulation off by tagging your scenario with @no-js-emulation.
# Turning on browser testing with @selenium, @culerity, @celerity or @javascript
# will also turn off the emulation. (See the Capybara documentation for
# details about those tags). If any of the browser tags are present, Cucumber-Rails
# will also turn off transactions and clean the database with DatabaseCleaner
# after the scenario has finished. This is to prevent data from leaking into
# the next scenario.
#
# Another way to avoid Cucumber-Rails' javascript emulation without using any
# of the tags above is to modify your views to use <button> instead. You can
# see how in http://github.com/jnicklas/capybara/issues#issue/12
#
Scenario: Delete authentication
Given the following authentications:
||
||
||
||
||
When I delete the 3rd authentication
Then I should see the following authentications:
||
||
||
||
Version data entries
7 entries across 7 versions & 1 rubygems