One of the problems could be that your routing specs is in the wrong
directory. Make sure all your routing specs go into 'spec/routing'
directory. Hope that helps.
--
Posted via http://www.ruby-forum.com/.
___
rspec-users mailing list
rspec-users@ruby
Hi,
Given i'm developing report charts with some data(on activerecord), i
want to know what would be tested in this case ?
For ex. A report for amount of created users along the time.
thank you
___
rspec-users mailing list
rspec-users@rubyforge.org
http
Thank you so much Justin. Crystal clear now.
Regards,
Gustavo Delfino
On May 26, 2011, at 12:05 AM, Justin Ko wrote:
> Actually, the lambda approach won't work, because you're carrying state
> (@index & @width) that is outside of scope in the matcher. This is what it
> would look like though:
Hi All,
New to rspec. Done some Rails, done TDD in other languages, trying to get the
two to meet. Getting a syntax error on my first routing spec:
context "public routing" do
it "routes / to public#landing" do
{ :get => "/" }.should route_to{:controller => "public", :action =>
"landing"}
On May 26, 2011, at 11:51 AM, Peter Bell wrote:
> Hi All,
>
> New to rspec. Done some Rails, done TDD in other languages, trying to get the
> two to meet. Getting a syntax error on my first routing spec:
>
> context "public routing" do
> it "routes / to public#landing" do
>{ :get => "/" }.
> This changed in 2.6, and I'd be willing to change it back (as it represents a
> regression in a minor release), but I'd prefer not to.
It did bite me, but I almost like the explicitness more...
-roger-
___
rspec-users mailing list
rspec-users@rubyfor
