rake spec:javascript ran in the wrong rails environment

[RobertAudi]

This might be a special case but it's a issue nonetheless. The rake spec:javascript command runs the specs in the wrong environment; that is, not in the test environment. I am using SSL in my app, which I've disabled in the test environment and I redirect all non-HTTPS traffic to their HTTPS equivalent (again, disabled in the test environment). When I ran rake spec:javascript I got the following error:

Jasmine runner at '/specs' returned a 301 error: Moved Permanently

This error is logical in my case, but I think that the rake task should run in the test environment anyway.

I managed to avoid the error using the following command:

RAILS_ENV=test rake spec:javascript

[kpolitowicz]

+1

It caused a snowball of problems when I couldn't make jasmine-spec.js uncompressed no matter what I changed in config/environments/test.rb which prompted me to bug good people at angular/angular.js#3534

[tvdeyen]

+1 👍

[gkop]

+1

[searls]

We've run into a bunch of problems trying to force rails to set the test environment from the rake task. To my knowledge the only way to do it would be to shell out inside the task in the event it's set to any other mode. PRs welcome

[searls]

I have an idea for a PR that would fix this problem. -- what if the rake task detected whether force_ssl was turned on and if so, specified "https" in the URL passed off to phantom?

[searls]

This is fixed in https://github.com/searls/jasmine-rails/releases/tag/v0.12.0 by #173