fix broken tests + update gemspec / readme
This commit is contained in:
parent
587d383ac5
commit
eb37cdcf36
@ -58,7 +58,7 @@ GEM
|
||||
bson (1.3.1)
|
||||
bson_ext (1.3.1)
|
||||
builder (2.1.2)
|
||||
bushido (0.0.27)
|
||||
bushido (0.0.29)
|
||||
highline (>= 1.6.1)
|
||||
json (>= 1.4.6)
|
||||
rest-client (>= 1.6.1)
|
||||
@ -245,8 +245,8 @@ GEM
|
||||
s3 (0.3.8)
|
||||
proxies (~> 0.2.0)
|
||||
sass (3.1.2)
|
||||
selenium-webdriver (0.2.1)
|
||||
childprocess (>= 0.1.7)
|
||||
selenium-webdriver (0.2.2)
|
||||
childprocess (>= 0.1.9)
|
||||
ffi (>= 1.0.7)
|
||||
json_pure
|
||||
rubyzip
|
||||
|
@ -19,7 +19,7 @@ h2. Gems
|
||||
|
||||
Here is a short list of main gems used in the application.
|
||||
|
||||
* Rails 3.0.8
|
||||
* Rails 3.0.9
|
||||
* Mongoid 2.0.2 (with MongoDB 1.6)
|
||||
* Liquid
|
||||
* Devise
|
||||
|
@ -15,7 +15,7 @@ Scenario: Pages list is not accessible for non authenticated accounts
|
||||
Scenario: Creating a valid page
|
||||
When I go to pages
|
||||
And I follow "new page"
|
||||
And I fill in "Title" with "Test"
|
||||
And I fill in "page_title" with "Test"
|
||||
And I fill in "Slug" with "test"
|
||||
And I select "Home page" from "Parent"
|
||||
And I fill in "Raw template" with "Lorem ipsum...."
|
||||
@ -26,7 +26,7 @@ Scenario: Creating a valid page
|
||||
Scenario: Updating a valid page
|
||||
When I go to pages
|
||||
And I follow "Home page"
|
||||
And I fill in "Title" with "Home page !"
|
||||
And I fill in "page_title" with "Home page !"
|
||||
And I fill in "Raw template" with "My new content is here"
|
||||
And I press "Update"
|
||||
Then I should see "Page was successfully updated."
|
||||
|
@ -17,7 +17,7 @@ Gem::Specification.new do |s|
|
||||
s.required_rubygems_version = ">= 1.3.6"
|
||||
s.rubyforge_project = "nowarning"
|
||||
|
||||
s.add_dependency "rails", ">= 3.0.8"
|
||||
s.add_dependency "rails", ">= 3.0.9"
|
||||
s.add_dependency "warden"
|
||||
s.add_dependency "devise", "1.3.4"
|
||||
s.add_dependency "mongoid", "2.0.2"
|
||||
|
Loading…
Reference in New Issue
Block a user