Changesets can be listed by changeset number.
The Git repository is here.
- Revision:
- 373
- Log:
Initial import of Radiant 0.9.1, which is now packaged as a gem. This is an
import of the tagged 0.9.1 source checked out from GitHub, which isn't quite
the same as the gem distribution - but it doesn't seem to be available in an
archived form and the installed gem already has modifications, so this is
the closest I can get.
- Author:
- rool
- Date:
- Mon Mar 21 13:40:05 +0000 2011
- Size:
- 2626 Bytes
1 | # IMPORTANT: This file is generated by cucumber-rails - edit at your own peril. |
2 | # It is recommended to regenerate this file in the future when you upgrade to a |
3 | # newer version of cucumber-rails. Consider adding your own code to a new file |
4 | # instead of editing this one. Cucumber will automatically load all features/**/*.rb |
5 | # files. |
6 | |
7 | ENV["RAILS_ENV"] ||= "cucumber" |
8 | require File.expand_path(File.dirname(__FILE__) + '/../../config/environment') |
9 | |
10 | require 'cucumber/formatter/unicode' # Remove this line if you don't want Cucumber Unicode support |
11 | require 'cucumber/rails/rspec' |
12 | require 'cucumber/rails/world' |
13 | require 'cucumber/rails/active_record' |
14 | require 'cucumber/web/tableish' |
15 | |
16 | require 'webrat' |
17 | require 'webrat/core/matchers' |
18 | |
19 | Webrat.configure do |config| |
20 | config.mode = :rails |
21 | config.open_error_files = false # Set to true if you want error pages to pop up in the browser |
22 | end |
23 | |
24 | |
25 | # If you set this to false, any error raised from within your app will bubble |
26 | # up to your step definition and out to cucumber unless you catch it somewhere |
27 | # on the way. You can make Rails rescue errors and render error pages on a |
28 | # per-scenario basis by tagging a scenario or feature with the @allow-rescue tag. |
29 | # |
30 | # If you set this to true, Rails will rescue all errors and render error |
31 | # pages, more or less in the same way your application would behave in the |
32 | # default production environment. It's not recommended to do this for all |
33 | # of your scenarios, as this makes it hard to discover errors in your application. |
34 | ActionController::Base.allow_rescue = false |
35 | |
36 | # If you set this to true, each scenario will run in a database transaction. |
37 | # You can still turn off transactions on a per-scenario basis, simply tagging |
38 | # a feature or scenario with the @no-txn tag. If you are using Capybara, |
39 | # tagging with @culerity or @javascript will also turn transactions off. |
40 | # |
41 | # If you set this to false, transactions will be off for all scenarios, |
42 | # regardless of whether you use @no-txn or not. |
43 | # |
44 | # Beware that turning transactions off will leave data in your database |
45 | # after each scenario, which can lead to hard-to-debug failures in |
46 | # subsequent scenarios. If you do this, we recommend you create a Before |
47 | # block that will explicitly put your database in a known state. |
48 | Cucumber::Rails::World.use_transactional_fixtures = true |
49 | |
50 | # How to clean your database when transactions are turned off. See |
51 | # http://github.com/bmabey/database_cleaner for more info. |
52 | if defined?(ActiveRecord::Base) |
53 | begin |
54 | require 'database_cleaner' |
55 | DatabaseCleaner.strategy = :truncation |
56 | rescue LoadError => ignore_if_database_cleaner_not_present |
57 | end |
58 | end |