Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Boxiang Sun
gitlab-ce
Commits
9f25657a
Commit
9f25657a
authored
Sep 10, 2012
by
Nihad Abbasov
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
modify env file for spinach
parent
decb3abf
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
57 deletions
+7
-57
features/support/env.rb
features/support/env.rb
+7
-57
No files found.
features/support/env.rb
View file @
9f25657a
unless
ENV
[
'CI'
]
require
'simplecov'
SimpleCov
.
start
'rails'
end
ENV
[
'RAILS_ENV'
]
=
'test'
require
'./config/environment'
require
'
cucumber/rails
'
require
'
webmock/cucumb
er'
require
'
rspec
'
require
'
database_clean
er'
WebMock
.
allow_net_connect!
require
Rails
.
root
.
join
'spec/support/gitolite_stub'
require
Rails
.
root
.
join
'spec/support/stubbed_repository'
require
Rails
.
root
.
join
'spec/support/login_helpers'
require
Rails
.
root
.
join
'spec/support/valid_commit'
Capybara
.
default_selector
=
:css
Capybara
.
javascript_driver
=
:webkit
# By default, any exception happening in your Rails application will bubble up
# to Cucumber so that your scenario will fail. This is a different from how
# your application behaves in the production environment, where an error page will
# be rendered instead.
#
# Sometimes we want to override this default behaviour and allow Rails to rescue
# exceptions and display an error page (just like when the app is running in production).
# Typical scenarios where you want to do this is when you test your error pages.
# There are two ways to allow Rails to rescue exceptions:
#
# 1) Tag your scenario (or feature) with @allow-rescue
#
# 2) Set the value below to true. Beware that doing this globally is not
# recommended as it will mask a lot of errors for you!
#
ActionController
::
Base
.
allow_rescue
=
false
# Remove/comment out the lines below if your app doesn't have a database.
# For some databases (like MongoDB and CouchDB) you may need to use :truncation instead.
begin
DatabaseCleaner
.
strategy
=
:transaction
rescue
NameError
raise
"You need to add database_cleaner to your Gemfile (in the :test group) if you wish to use it."
end
Cucumber
::
Rails
::
Database
.
javascript_strategy
=
:truncation
require
'headless'
headless
=
Headless
.
new
headless
.
start
require
'cucumber/rspec/doubles'
include
GitoliteStub
Before
do
stub_gitolite!
end
World
(
FactoryGirl
::
Syntax
::
Methods
)
DatabaseCleaner
.
strategy
=
:transaction
Spinach
.
hooks
.
before_scenario
{
DatabaseCleaner
.
start
}
Spinach
.
hooks
.
after_scenario
{
DatabaseCleaner
.
clean
}
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment