Remove unused tests

pull/6827/head
Mark Maglana 14 years ago
parent b4e7ee10a4
commit 107f89be8e
  1. 50
      features/manage_stories.feature
  2. 14
      features/step_definitions/story_steps.rb

@ -1,50 +0,0 @@
Feature: Manage stories
In order to track project progress
Product Owner, Scrum Master, and Team Members
want to manage stories
Scenario: Something
Given I am on the home page
# Scenario: Register new story
# Given I am on the new story page
# When I fill in "Subject" with "subject 1"
# And I press "Create"
# Then I should see "subject 2"
# 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 story
# Given the following stories:
# |subject|
# |subject 1|
# |subject 2|
# |subject 3|
# |subject 4|
# When I delete the 3rd story
# Then I should see the following stories:
# |Subject|
# |subject 1|
# |subject 2|
# |subject 4|

@ -1,14 +0,0 @@
Given /^the following stories:$/ do |stories|
Story.create!(stories.hashes)
end
When /^I delete the (\d+)(?:st|nd|rd|th) story$/ do |pos|
visit stories_path
within("table tr:nth-child(#{pos.to_i+1})") do
click_link "Destroy"
end
end
Then /^I should see the following stories:$/ do |expected_stories_table|
expected_stories_table.diff!(tableish('table tr', 'td,th'))
end
Loading…
Cancel
Save