On Mon, Jun 25, 2012 at 6:49 PM, Avi Tzurel wrote:
> Problem solved (although I am not sure where the bug is and if it's a bug).
>
> the initializers folder had modules defined in it (Facebook, Web).
> Those modules were not loading with Rails when Rspec was loading the
> environment and were not
Problem solved (although I am not sure where the bug is and if it's a bug).
the initializers folder had modules defined in it (Facebook, Web).
Those modules were not loading with Rails when Rspec was loading the
environment and were not defined as modules in the constants.
When I moved those mo
Sure, no problem
here's the error message
https://gist.github.com/2991793
This is my spec_helper file
https://gist.github.com/2991803
The class that is missing is Web which actually does exist in initializers
https://gist.github.com/2991809
--
Sincerely,
Avi Tzurel
English blog: http://www.
On Mon, Jun 25, 2012 at 6:07 PM, Avi Tzurel wrote:
> Hi,
>
> We upgraded our app from 3.0.9 to 3.2.5.
> Latest Rspec version running of course.
>
> When I run rspec command, I get uninitialized constant error.
> The constant that Rspec is alerting on is in the initializers class.
>
> it seems that
Hi,
We upgraded our app from 3.0.9 to 3.2.5.
Latest Rspec version running of course.
When I run rspec command, I get uninitialized constant error.
The constant that Rspec is alerting on is in the initializers class.
it seems that Rspec is not running the Rails initializers.
Anyone else had/know
