#4458 [BUG] [PATCH] Rails 3.0 should allow tests to run in 'cucumber' environment - Ruby on Rails

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

This project is archived and is in readonly mode.

#4458 ✓resolved

[BUG] [PATCH] Rails 3.0 should allow tests to run in 'cucumber' environment

Reported by Philippe Creux | April 22nd, 2010 @ 06:58 PM | in 3.0.5

rails/railties/lib/rails/test_help.rb aborts if the environment is not 'test'. See: http://github.com/rails/rails/blob/master/railties/lib/rails/test_h...

I can't run Cucumber/RSpec/Test_Unit tests in different environments then.

I attach a path so that it aborts testing if the environment is development or production.

Edit: That's in Rails 3.0. Looks like I can't update the milestone. Sorry for this. :-/

abort_testing_in_dev_or_prod.diff 931 Bytes

Comments and changes to this ticket

You flagged this item as spam.
Philippe Creux April 22nd, 2010 @ 07:05 PM
- Title changed from “Rails should allow test to run in 'cucumber' environment” to “Rails 3.0 should allow tests to run in 'cucumber' environment”
You flagged this item as spam.
Philippe Creux April 22nd, 2010 @ 07:06 PM
- Tag set to “rails 3, cucumber, environement, environments, rspec”
- Title changed from “Rails 3.0 should allow tests to run in 'cucumber' environment” to “[BUG] [PATCH] Rails 3.0 should allow tests to run in 'cucumber' environment”
Rizwan Reza May 15th, 2010 @ 03:14 PM
- Milestone cleared.
- State changed from “new” to “open”
I am kinda skeptical on this one. The patch checks for development and production environment only while there's a good chance for a lot of Rails developers to define staging environment (much like production), among others.

I don't know, may be an environment variable can be taken into account when it's present?
Rizwan Reza May 15th, 2010 @ 03:14 PM
- Tag changed from “rails 3, cucumber, environement, environments, rspec” to “rails 3, bugmash, cucumber, environement, environments, rspec”
You flagged this item as spam.
elcuervo May 15th, 2010 @ 06:01 PM
Perhaps changing ActiveSupport::StringInquirer and making it able to, depending on a [environment].rb, use a config.test = true or something like that?
You flagged this item as spam.
Trotter Cashion August 3rd, 2010 @ 01:22 AM
- Importance changed from “” to “Low”
Seems like having config.test_env = true is worthwhile. We (Trevor Menagh, Sean Greive, Trotter Cashion) created this patch to do just that. Will allow alternate test environments to declare themselves as test_envs.
- add-config-test-env.diff 2 KB
Jeremy Kemper August 30th, 2010 @ 04:10 AM
- Milestone cleared.
[bulk edit]
Jeremy Kemper October 15th, 2010 @ 11:01 PM
- Milestone set to “3.0.2”
[bulk edit]
Ryan Bigg October 19th, 2010 @ 08:34 AM
- Tag cleared.
Automatic cleanup of spam.
Santiago Pastorino November 15th, 2010 @ 09:15 PM
- Milestone cleared.
[bulk edit]
You flagged this item as spam.
Cesario November 24th, 2010 @ 07:38 PM
This ticket can be closed safely, the new condition is Abort if Rails.env.production?
https://github.com/rails/rails/commit/672ce11d684e1211836ca22cf5b0c...
Rohit Arondekar December 12th, 2010 @ 02:17 AM
- State changed from “open” to “resolved”
Santiago Pastorino February 12th, 2011 @ 09:58 PM
- Milestone set to “3.0.5”
[bulk edit]