Myron Marston wrote:
>> Factory's are nice but they make your tests very slow.
>
> This has been my experience, too.
Though not mine as far as I can tell. Which factory library are you
using? I use Machinist.
Best,
--
Marnen Laibow-Koser
http://www.marnen.org
mar...@marnen.org
--
Posted vi
Check out this (my) presentation:
http://bit.ly/grease-your-suite-html
arrow keys navigate.
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyonrails-t...
> Factory's are nice but they make your tests very slow.
This has been my experience, too. I attempted to solve it (with some
measure of success) with my factory_data_preloader gem:
http://github.com/myronmarston/factory_data_preloader/tree/master
You can also benchmark your tests to see where
So far, this is the fastest solution I can find:
Dataset with rails-test-serving
http://github.com/Roman2K/rails-test-serving
http://github.com/aiwilliams/dataset
I was able to cut down a test file from 15 seconds to 2 seconds using
dataset's "create_record" method, which bypasses validations.
Hey guys, thanks for all the suggestions! Sorry, I meant 30 seconds
*each test file*, not the entire suite. Whenever I run 'rake', I
always switch over and do something else for awhile because it takes
so long.
Have you guys seen this? http://www.devver.net/
Hopefully this will help a problem wh
Greg Donald wrote:
>
> 30 seconds isn't bad at all.
True, but you probably wouldn't want it to be any longer than that if
you're using autotest or similar.
[...]
>
> You might try moving your unit tests into memory.
>
> http://www.thoughtbot.com/projects/factory_girl/
He already said he was
The apps I work on at work have 180+ models each. There isn't
duplication, but just way too many features. :(
What Greg said works pretty well for us - factory_girl or any of the
other factory libraries are great.
You could also mock the AR find/delete/create/update calls if you want
and return
On Wed, May 27, 2009 at 12:02 PM, jko170 wrote:
>
> My app has 64 models and my test are so slow. 30 seconds at least.
30 seconds isn't bad at all.
> I'm using Machinist. How can I speed up my tests? It has really killed
> my motivation to test at all...
>
> I'm using rails-test-serve but that
Phlip wrote:
> jko170 wrote:
>
>> My app has 64 models and my test are so slow. 30 seconds at least.
>
> Projects should not require so many models. Does your design have any
> duplication?
That's a lot of models, but I wonder if that's the problem. I'm having
a problem with *extremely* slow
jko170 wrote:
> My app has 64 models and my test are so slow. 30 seconds at least.
Projects should not require so many models. Does your design have any
duplication?
> I'm using Machinist. How can I speed up my tests? It has really killed
> my motivation to test at all...
Can you still TDD by
On Wed, May 27, 2009 at 1:02 PM, jko170 wrote:
>
> My app has 64 models and my test are so slow. 30 seconds at least.
>
> I'm using Machinist. How can I speed up my tests? It has really killed
> my motivation to test at all...
>
> I'm using rails-test-serve but that only brings the test down to 1
jko170 wrote:
> My app has 64 models and my test are so slow. 30 seconds at least.
>
> I'm using Machinist. How can I speed up my tests? It has really killed
> my motivation to test at all...
30 seconds? I'll take that any day! :-)
I am involved in one project that has a test suite which takes
12 matches
Mail list logo
