Re: Optimise PostgreSQL for fast testing

From: David Salisbury <salisbury(at)globe(dot)gov>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Optimise PostgreSQL for fast testing
Date: 2012-02-23 17:05:45
Message-ID: 4F4671E9.404@globe.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2/23/12 9:06 AM, Jack Christensen wrote:
> As another Rails developer using PostgreSQL I think I can explain the
> use case. In standard Rails usage, the ORM handles all SQL query
> generation and thus the application is database agnostic. It is typical
> to use SQLite in development and testing and MySQL or PostgreSQL in
> production. However, if any PostgreSQL specific functionality is used
> then obviously PostgreSQL must also be used in development and testing.
>
> Another common practice is test-driven development. So the test suite
> for the application may run scores or hundreds of times per day per
> developer. So the speed of the test suite is of vital importance to
> developers. A 30 second difference 100's of times per day really can add
> up.

Perhaps the emphasis should be on the tests themselves, and not PG cycles.
Is he using Factory or Factory.build?.. that sort of thing. Is he running
the entire test suite, when in fact just running one test would do until
final checkin?

And I'm curious as to why anyone would need to run tests 100s of times a day.
How much code can ya write, or is he simply writing tests themselves all day?

-ds

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2012-02-23 17:20:37 Re: Optimise PostgreSQL for fast testing
Previous Message John R Pierce 2012-02-23 16:41:44 Re: How to enable thread safety on postgresql 8.3.6