waterline

So basically their biggest problem was that node.js machine-gun hammers the filesystem with stat calls when looking for modules. This was made worse by running on a shared folder. Vagrant has a mode called rsync-auto which will synchronize directories into a local vm. Or you could just always have the code local to the node process. It makes more sense to have your editor work with remote files. Next biggest problem was relational database. I think that tests requiring a SQL database are usually a bad sign, and the statement "we'd like to use transactions but our orm doesn't support them" makes me sad. To paraphrase Ben Franklin, "those who would give up transactions for a framework deserve neither". Here's some ideas for speeding up your tests, in order from best to worst. - Make most business code rely on a service or interface. Swap

This is a nice guide on setting up integration with a PostgreSQL database from Node. I've come across a few projects recently that make similar attempts, as an ORM: Bookshelf: http://bookshelfjs.org/ Sequelize: http://sequelizejs.com/ Waterline: https://github.com/balderdashy/waterline