El 08/07/2010, a las 04:45, Lalish-Menagh, Trevor escribió:
> OK, here is an idea. I was thinking about how to make routing tests
> that make sense. I agree with Wincent that the Rails verbiage for the
> routing tests is confusing, but what is NOT confusing is the new
> routing format, so why not
OK, here is an idea. I was thinking about how to make routing tests
that make sense. I agree with Wincent that the Rails verbiage for the
routing tests is confusing, but what is NOT confusing is the new
routing format, so why not try out this format
(http://gist.github.com/467563):
describe 'routi
On Jul 7, 2010, at 8:22 AM, Andrew Premdas wrote:
> Hi there.
>
> My understanding (which is limited) is that rspec uses at_exit to run its
> specs. I don't really know why - could somoene explain?
The initial motivation was that it makes it easy to make sure it works whether
you run it with t
El 07/07/2010, a las 16:42, David Chelimsky escribió:
> On Jul 7, 2010, at 7:39 AM, Wincent Colaiuta wrote:
>
>> El 07/07/2010, a las 13:29, David Chelimsky escribió:
>
> How about going back to map, with to_and_from:
>
> it { should map(get "/issues/new").to_and_from("issues#new") }
>
>
On Jul 7, 2010, at 7:39 AM, Wincent Colaiuta wrote:
> El 07/07/2010, a las 13:29, David Chelimsky escribió:
>
>> Seems as though this format has been abandoned in this conversation:
>>
>> it { should route(get "/issues/new").to("issues#new") }
>> it { should generate("/issues/new").from("issues
El 07/07/2010, a las 13:29, David Chelimsky escribió:
> Seems as though this format has been abandoned in this conversation:
>
> it { should route(get "/issues/new").to("issues#new") }
> it { should generate("/issues/new").from("issues#new") }
>
> I think that verbiage is concise and intention
Hi there.
My understanding (which is limited) is that rspec uses at_exit to run its
specs. I don't really know why - could somoene explain?
My problem with this behaviour is that I would like the running of a spec to
start an instance of solr (using Sunspot) if one is not running. The problem
wit
Hi,
Ive installed the remarkable_rails plugin(3.1.13) so i can use the
macros to test the model associations and validations.
For my model user i have:
validates_presence_of :title, :message => 'cannot be blank!'
validates_length_of :title, :within => 2..40, :too_short => 'is
too short!',
On Jul 7, 2010, at 1:24 AM, Wincent Colaiuta wrote:
> El 07/07/2010, a las 01:16, Lalish-Menagh, Trevor escribió:
>
>> Hi David,
>>
>> You make a good point. I was talking with a coworker about this
>> problem, and he suggested a simpler format, that I think will coincide
>> some with Wincent's
On Jul 7, 2010, at 5:26 AM, Trevor Lalish-Menagh wrote:
>> Did you know about the rspec-dev meta project?
>>
>> http://github.com/rspec/rspec-dev
>
> That is great. I should have looked for that before setting this up. I just
> didn't think about it.
>
>> Perhaps we should update the rspec-*
> Did you know about the rspec-dev meta project?
>
> http://github.com/rspec/rspec-dev
That is great. I should have looked for that before setting this up. I just
didn't think about it.
> Perhaps we should update the rspec-* READMEs with a point back to rspec-dev
> so that people know about i
El 07/07/2010, a las 03:54, Lalish-Menagh, Trevor escribió:
> I am sure most of you could do this easily, but I wanted to write down
> how I got there in any case, so here are my instructions on how to set
> up rspec-rails to hack on:
> http://trevmex.com/post/779078048/how-to-start-hacking-a-ruby
12 matches
Mail list logo
