attempt to get travis to test on psql not sqlite
fixed c&p error in database.yml
load test gems in travis environment too
set up test users in travis environment
gave up on not_staff, shuffling interesting members instead
Can't assume we have a member with id = 1

this works on sqlite but not on postgres (which we now test on, on
travis)
cleaning up tests on postgres

- still trying to make sure we explicitly use a real member, not just
assume there's one with id = 1

- also it looks like the tests for post activity are passing for obscure
reasons on sqlite when they shouldn't be. this is a known bug
(https://www.pivotaltracker.com/story/show/51280861) apparently
invisible to us under sqlite.
removed boring tests from controllers

the tests generated by 'rails g scaffold...' are boring and brittle.
they don't actually test anything other than the rails framework, and
they were causing us all kinds of trouble. we've started to blow them
away (and raised a PT chore to remove them from other controllers in due
course).
cleaned up boring controller tests
Fixed failing timestamp test on postgres
Merge branch 'dev' into staff
Removed test user seeding from test/travis envs

We don't actually use these for testing (and shouldn't).
Cleaned up seeds.rb, added methods etc.

Also ensured that things that are needed in production are created in
production: staff and free account types, admin and wrangler roles.
Merge pull request #247 from Skud/staff

Lots of stuff, including staff on homepage, testing on postgres, and various others