Ensuring that the test/dummy/db directory exists.

Tests fail, being unable to create the sqlite database, when in fact
the db directory doesn't exist to create the databases in.

Signed-off-by: Chris Riddoch <criddoch@globe.gov>
Removing older tests, will integrate into the rails dummy app as time allows

Signed-off-by: Chris Riddoch <criddoch@globe.gov>
Creating documents table, and defining the model with acts_as_versioned

Signed-off-by: Chris Riddoch <criddoch@globe.gov>
Some basic tests for whether a new version should be created on save

Signed-off-by: Chris Riddoch <criddoch@globe.gov>
Reset test database in dummy rails project before running tests.

The 'rake test' task in the main project doesn't seem to run anything
in the dummy rails project by default, and the tests expect that the
database is created and migrations have been run.  This implicitly
tests the migration helper.

Signed-off-by: Chris Riddoch <criddoch@globe.gov>
Set track_altered_attributes based on calculation of non_versioned_columns for defaults.

This addresses the issue in which a version is created despite only
non-versioned columns being modified.

Signed-off-by: Chris Riddoch <criddoch@globe.gov>
Be sure tests complain on failure

Signed-off-by: Chris Riddoch <criddoch@globe.gov>
'comments' fields don't belong in this project.

That's for a particular use of acts_as_versioned, not generic.

Signed-off-by: Chris Riddoch <criddoch@globe.gov>