News for hackers. Stuff that matters.
Re:Postgression - A PostgreSQL database for every test case by rdegges on Monday January 21, 2013 @08:50PM (#5095028)
Hi Titanous, you're definitely right--the focus of postgression isn't speed, just convenience.

Installing a database server locally to run unit tests is something that has always annoyed me. 99.99% of the time when I'm testing things, I'm at a computer, hooked up to the internet, working on things--and I'm usually not all that concerned about an extra second of overhead.

I think the real benefit to this is that you can use the same DB harness regardless of where you're testing: locally, Jenkins, Travis-CI, whatever. This way, you don't have to write any code to make databases, check credentials, whatever, it's just a thoughtless process.

Re:Postgression - A PostgreSQL database for every test case by Titanous on Monday January 21, 2013 @08:58PM (#5095058)
I understand the premise, but this isn't performant enough to be used for anything but the smallest of projects. It isn't just "an extra second of overhead", it increased a 15 second test run to 15 minutes for me (on a fast fiber connection).

Locally I already have Postgres installed for development, and Travis does as well. I guess this might be useful for Jenkins on EC2 in the same AZ as Heroku Postgres, but the latency is still going to be painful.

Re:Postgression - A PostgreSQL database for every test case by nirvdrum on Monday January 21, 2013 @11:01PM (#5095436)
Sorry, I'm trying to wrap my head around the workflow. Do you use vagrant or something for tests? Othrewise, wouldn't you need the DB installed locally to run your site locally?
Re:Postgression - A PostgreSQL database for every test case by rdegges on Tuesday January 22, 2013 @03:00AM (#5096096)
I always use a remote db for developing my site locally (eg: Heroku PostgreSQL). On my laptop I typically install my libraries (in a Python virtualenv), and do coding.