test_data 0.2.2 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 18d3469e9d0173f81ef3b2d8d082861094d79354b8fb544e983bdcfdd8eb788b
-  data.tar.gz: 983a1645132b22024799670ec463f11fe5f8e0d1b9427b96940dea8c684fbafb
+  metadata.gz: 8c9bcdeaebcbad6163fb495b327408b64f7d85f90efd7ab171275ba4fd61e484
+  data.tar.gz: c08433086b9cfcb57e88e275e63f8600083945afdd738962a952e94573b95f77
 SHA512:
-  metadata.gz: c7fb1b86f23f074bb185cb1cf11c437d4ba57445d65907509384838993628c5759803ee90f3f290dbb219754806bb1c1133b7e84bf430918c1a23b3fca86b752
-  data.tar.gz: d00e512b415c74ab1650a3b3d58e36759d085056375e07326d8790d0033bc18066a2d82c791a578fb9d11cb7c08f9056d4d5e380b9cc52f97dd467c245469771
+  metadata.gz: e69305fb469eab8714569cea4b57fb6a3b9050ea97065230ef86afa27e8c089d094b75673515348e31f8ec989a61924fb7924d70c21fdbd31decdef8e490459e
+  data.tar.gz: 1592fccf3753f33c74f449ad2debe029806778383fd07f089c9bb67e49861e5a3885d04497720dd04525511182ca8b87ff6774c90837845204f210d85f3db270

data/CHANGELOG.md

@@ -1,3 +1,12 @@
+# 0.3.0
+
+- Add a `test_data:reinitialize` task that will delete the `test_data` database
+  if necessary before invoking `test_data:initialize`
+  - Warn if re-initializing and the local database appears to have been dumped
+    or loaded from a dump that is newer than the dumps on disk
+- Add a warning on app load if the dumps on disk appear
+  newer than the local `test_data` database
+
 # 0.2.2
 
 - Improve performance of Rails fixtures being repeatedly loaded by changing the

data/Gemfile.lock

@@ -1,26 +1,26 @@
 PATH
   remote: .
   specs:
-    test_data (0.2.2)
+    test_data (0.3.0)
       railties (~> 6.0)
 
 GEM
   remote: https://rubygems.org/
   specs:
-    actionpack (6.1.4)
-      actionview (= 6.1.4)
-      activesupport (= 6.1.4)
+    actionpack (6.1.4.1)
+      actionview (= 6.1.4.1)
+      activesupport (= 6.1.4.1)
       rack (~> 2.0, >= 2.0.9)
       rack-test (>= 0.6.3)
       rails-dom-testing (~> 2.0)
       rails-html-sanitizer (~> 1.0, >= 1.2.0)
-    actionview (6.1.4)
-      activesupport (= 6.1.4)
+    actionview (6.1.4.1)
+      activesupport (= 6.1.4.1)
       builder (~> 3.1)
       erubi (~> 1.4)
       rails-dom-testing (~> 2.0)
       rails-html-sanitizer (~> 1.1, >= 1.2.0)
-    activesupport (6.1.4)
+    activesupport (6.1.4.1)
       concurrent-ruby (~> 1.0, >= 1.0.2)
       i18n (>= 1.6, < 2)
       minitest (>= 5.1)
@@ -34,13 +34,13 @@ GEM
     erubi (1.10.0)
     i18n (1.8.10)
       concurrent-ruby (~> 1.0)
-    loofah (2.11.0)
+    loofah (2.12.0)
       crass (~> 1.0.2)
       nokogiri (>= 1.5.9)
     method_source (1.0.0)
     mini_portile2 (2.6.1)
     minitest (5.14.4)
-    nokogiri (1.12.0)
+    nokogiri (1.12.4)
       mini_portile2 (~> 2.6.1)
       racc (~> 1.4)
     parallel (1.20.1)
@@ -56,11 +56,11 @@ GEM
     rails-dom-testing (2.0.3)
       activesupport (>= 4.2.0)
       nokogiri (>= 1.6)
-    rails-html-sanitizer (1.3.0)
+    rails-html-sanitizer (1.4.2)
       loofah (~> 2.3)
-    railties (6.1.4)
-      actionpack (= 6.1.4)
-      activesupport (= 6.1.4)
+    railties (6.1.4.1)
+      actionpack (= 6.1.4.1)
+      activesupport (= 6.1.4.1)
       method_source
       rake (>= 0.13)
       thor (~> 1.0)

data/README.md

@@ -61,6 +61,7 @@ we have reckoned with to this point.
     * [test_data:configure](#test_dataconfigure)
     * [test_data:verify_config](#test_dataverify_config)
     * [test_data:initialize](#test_datainitialize)
+    * [test_data:reinitialize](#test_datareinitialize)
     * [test_data:dump](#test_datadump)
     * [test_data:load](#test_dataload)
     * [test_data:create_database](#test_datacreate_database)
@@ -430,23 +431,21 @@ to update your test data. Here's how to do it:
     1. Be sure there's nothing in your local `test_data` database that you added
        intentionally and forgot to dump, because it's about to be erased
 
-    2. Run `rake test_data:drop_database`
+    2. Run `rake test_data:reinitialize` drop and recreate the `test_data`
+       database and load the latest SQL dumps into it
 
-    3. Run `rake test_data:load` to recreate the `test_data` database and load
-       the latest SQL dumps into it
+    3. Run any pending migrations with `RAILS_ENV=test_data bin/rake db:migrate`
 
-    4. Run any pending migrations with `RAILS_ENV=test_data bin/rake db:migrate`
-
-    5. If you need to create any additional data, start up the server
+    4. If you need to create any additional data, start up the server
        (`RAILS_ENV=test_data bin/rails s`), just like in [Step
        2](#step-2-create-some-test-data)
 
-    6. Export your newly-updated `test_data` database with `rake test_data:dump`
+    5. Export your newly-updated `test_data` database with `rake test_data:dump`
 
-    7. Ensure your tests are passing and then commit the resulting SQL files
+    6. Ensure your tests are passing and then commit the resulting SQL files
 
 * If the local `test_data` database is already up-to-date with the current SQL
-  dumps, follow steps **4 through 7** above
+  dumps, follow steps **3 through 6** above
 
 It's important to keep in mind that your test data SQL dumps are a shared,
 generated resource among your team (just like a `structure.sql` or `schema.rb`
@@ -664,6 +663,18 @@ your seed file. Specifically:
     * Otherwise, it invokes the task `db:schema:load` and `db:seed` (similar to
       Rails' built-in `db:setup` task)
 
+### test_data:reinitialize
+
+This task is designed for the situation where you may already have a `test_data`
+database created and simply want to drop it and replace it with whatever dumps
+are in the `test/support/test_data` directory.
+
+Dropping the database requires confirmation, either interactively or by setting
+the environment variable `TEST_DATA_CONFIRM`. It will additionally warn you in
+the event that the local database appears to be newer than the dumps on disk
+that would replace it. From there, this task behaves the same way as `rake
+test_data:initialize`.
+
 ### test_data:dump
 
 This task is designed to be run after you've created or updated your test data
@@ -775,8 +786,8 @@ There are two additional things to keep in mind if using this method:
 
 1. Using this feature requires that you've first invoked
    [TestData.prevent_rails_fixtures_from_loading_automatically!](#testdataprevent_rails_fixtures_from_loading_automatically)
-   to override Rails' default behavior before any of your tests have loaded or
-   started running
+   before your tests have started running to override Rails' default behavior
+   before any of your tests have loaded or started running
 
 2. Because the method depends on Rails' fixture caching mechanism, it must be
    passed an instance of the running test class (e.g.
@@ -1227,20 +1238,9 @@ result in a significantly slower overall test suite. Instead, if you group tests
 that use the same type of test data together (e.g. by separating them into
 separate suites), you might find profound speed gains.
 
-To illustrate why, suppose you have 5 tests that call `TestData.uses_test_data`
-and 5 that call `TestData.uses_rails_fixtures`. If a test that calls
-`TestData.uses_test_data` is followed by another that calls `uses_test_data`,
-the only operation needed by the second call will be a rollback to the savepoint
-taken after the test data was loaded. If, however, a `uses_test_data` test is
-followed by a `uses_rails_fixtures` test, then a lot more work is required:
-first a rollback, then the truncation of the test data, then a load of the
-fixtures followed by creation of a new savepoint—which would in tunr be undone
-again if the _next_ test happened to call `uses_test_data`. Switching between
-tests that use different sources of test data can cause significant unnecessary
-thrashing.
-
-To illustrate the above, if all of these tests ran in random order (the
-default), you might see:
+To illustrate this, suppose you had 5 tests that relied on your `test_data` data
+and 5 that relied on Rails fixtures. If all of these tests ran in random order
+(the default), you might see the following behavior at run-time:
 
 ```
 $ bin/rails test test/example_test.rb
@@ -1272,9 +1272,11 @@ data into sub-suites that are run serially, on e after the other.
   [minitest-suite](https://github.com/testdouble/minitest-suite) to accomplish
   exactly this. Just declare something like `suite :test_data` or `suite
   :fixtures` at the top of each test class
-* If you're using RSpec, the
-  [tag](https://relishapp.com/rspec/rspec-core/v/3-10/docs/command-line/tag-option)
-  feature can help you organize your tests by type, but you'll likely have to
+* If you're using RSpec, the [suite option combined with a custom
+  ordering](https://gist.github.com/myronmarston/8fea012b9eb21b637335bb29069bce6b)
+  can accomplish this. You might also consider using
+  [tags](https://relishapp.com/rspec/rspec-core/v/3-10/docs/command-line/tag-option)
+  to organize your tests by type, but you'll likely have to
   run a separate CLI invocation for each to avoid the tests from being
   interleaved
 

data/example/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: ..
   specs:
-    test_data (0.2.2)
+    test_data (0.3.0)
       railties (~> 6.0)
 
 GEM

data/lib/test_data/detects_database_existence.rb

@@ -0,0 +1,19 @@
+module TestData
+  class DetectsDatabaseExistence
+    def initialize
+      @config = TestData.config
+    end
+
+    def call
+      rows = ActiveRecord::Base.connection.execute <<~SQL
+        select datname database_name
+        from pg_catalog.pg_database
+      SQL
+      rows.any? { |row|
+        row["database_name"] == @config.database_name
+      }
+    rescue ActiveRecord::NoDatabaseError
+      false
+    end
+  end
+end

data/lib/test_data/determines_databases_associated_dump_time.rb

@@ -0,0 +1,13 @@
+module TestData
+  class DeterminesDatabasesAssociatedDumpTime
+    def call
+      if (last_dumped_at = ActiveRecord::InternalMetadata.find_by(key: "test_data:last_dumped_at")&.value)
+        Time.parse(last_dumped_at)
+      end
+    rescue ActiveRecord::StatementInvalid
+      # This will be raised if the DB exists but hasn't been migrated/schema-loaded
+    rescue ActiveRecord::NoDatabaseError
+      # This will be raised if the DB doesn't exist yet, which we don't need to warn about
+    end
+  end
+end

data/lib/test_data/determines_when_sql_dump_was_made.rb

@@ -0,0 +1,24 @@
+module TestData
+  class DeterminesWhenSqlDumpWasMade
+    def initialize
+      @config = TestData.config
+    end
+
+    def call
+      if (last_dumped_at = find_last_dumped_value)
+        Time.zone.parse(last_dumped_at)
+      end
+    end
+
+    private
+
+    def find_last_dumped_value
+      return unless File.exist?(@config.non_test_data_dump_path)
+      File.open(@config.non_test_data_dump_path, "r").each_line do |line|
+        if (match = line.match(/INSERT INTO public\.ar_internal_metadata VALUES \('test_data:last_dumped_at', '([^']*)'/))
+          return match[1]
+        end
+      end
+    end
+  end
+end

data/lib/test_data/dumps_database.rb

@@ -6,9 +6,12 @@ module TestData
   class DumpsDatabase
     def initialize
       @config = TestData.config
+      @records_dump_metadata = RecordsDumpMetadata.new
     end
 
     def call
+      @records_dump_metadata.call
+
       dump(
         type: :schema,
         database_name: @config.database_name,

data/lib/test_data/railtie.rb

@@ -8,5 +8,9 @@ module TestData
     rake_tasks do
       load Pathname.new(__dir__).join("rake.rb")
     end
+
+    initializer "test_data.validate_data_up_to_date" do
+      WarnsIfDumpIsNewerThanDatabase.new.call
+    end
   end
 end

data/lib/test_data/rake.rb

@@ -10,17 +10,18 @@ def run_in_test_data_env(task_name)
 end
 
 def create_database_or_else_blow_up_if_its_not_empty!
+  raise unless Rails.env.test_data?
+
+  unless TestData::DetectsDatabaseExistence.new.call
+    Rake::Task["test_data:create_database"].invoke
+  end
+
   unless TestData::DetectsDatabaseEmptiness.new.empty?
     raise TestData::Error.new("Database '#{TestData.config.database_name}' already exists and is not empty. To re-initialize it, drop it first (e.g. `rake test_data:drop_database`)")
   end
-rescue TestData::Error => e
-  raise e
-rescue
-  # Only (anticipated) cause for raise here is DB did not exist
-  Rake::Task["test_data:create_database"].invoke
 end
 
-desc "Verifies test_data environment looks good"
+desc "Verifies that the test_data environment looks good"
 task "test_data:verify_config" do
   TestData.log.with_plain_writer do
     config = TestData::VerifiesConfiguration.new.call
@@ -34,12 +35,12 @@ task "test_data:verify_config" do
   end
 end
 
-desc "Install default configuration files and snippets"
+desc "Installs default configuration files and snippets"
 task "test_data:configure" do
   TestData::InstallsConfiguration.new.call
 end
 
-desc "Initialize test_data's interactive database"
+desc "Initializes test_data's interactive database"
 task "test_data:initialize" => ["test_data:verify_config", :environment] do
   next run_in_test_data_env("test_data:initialize") if wrong_env?
 
@@ -59,7 +60,36 @@ task "test_data:initialize" => ["test_data:verify_config", :environment] do
   MSG
 end
 
-desc "Initialize test_data Rails environment & configure database"
+desc "Re-initializes test_data's interactive database (by dropping and reloading it)"
+task "test_data:reinitialize" => ["test_data:verify_config", :environment] do
+  next run_in_test_data_env("test_data:reinitialize") if wrong_env?
+
+  # Take caution only if the test_data database exists
+  if TestData::DetectsDatabaseExistence.new.call
+    TestData::WarnsIfDatabaseIsNewerThanDump.new.call
+
+    unless ENV["TEST_DATA_CONFIRM"].present?
+      confirmed = if $stdin.isatty
+        puts "This will DROP test_data database '#{TestData.config.database_name}'. Are you sure you want to re-initialize it? [yN]"
+        $stdin.gets.chomp.downcase.start_with?("y")
+      else
+        puts "'#{TestData.config.database_name}' exists. Set TEST_DATA_CONFIRM=true to drop the database and re-initialize it."
+        false
+      end
+
+      unless confirmed
+        puts "Exiting without making any changes"
+        exit 1
+      end
+    end
+
+    Rake::Task["test_data:drop_database"].invoke
+  end
+
+  Rake::Task["test_data:initialize"].invoke
+end
+
+desc "Initializes test_data Rails environment & configure database"
 task "test_data:install" => ["test_data:configure", "test_data:initialize"]
 
 desc "Dumps the interactive test_data database"

data/lib/test_data/records_dump_metadata.rb

@@ -0,0 +1,9 @@
+module TestData
+  class RecordsDumpMetadata
+    def call
+      ActiveRecord::InternalMetadata
+        .find_or_initialize_by(key: "test_data:last_dumped_at")
+        .update!(value: Time.now.utc.inspect)
+    end
+  end
+end

data/lib/test_data/version.rb

@@ -1,3 +1,3 @@
 module TestData
-  VERSION = "0.2.2"
+  VERSION = "0.3.0"
 end

data/lib/test_data/warns_if_database_is_newer_than_dump.rb

@@ -0,0 +1,32 @@
+module TestData
+  class WarnsIfDatabaseIsNewerThanDump
+    def initialize
+      @config = TestData.config
+      @determines_when_sql_dump_was_made = DeterminesWhenSqlDumpWasMade.new
+      @determines_databases_associated_dump_time = DeterminesDatabasesAssociatedDumpTime.new
+    end
+
+    def call
+      return unless Rails.env.test_data?
+      sql_dumped_at = @determines_when_sql_dump_was_made.call
+      database_dumped_at = @determines_databases_associated_dump_time.call
+
+      if database_dumped_at.present? &&
+          sql_dumped_at.present? &&
+          database_dumped_at > sql_dumped_at
+        TestData.log.warn <<~MSG
+          Your local test_data database '#{@config.database_name}' is associated
+          with a SQL dump that was NEWER than the current dumps located in
+          '#{File.dirname(@config.data_dump_path)}':
+
+            SQL Dump: #{sql_dumped_at.localtime}
+            Database: #{database_dumped_at.localtime}
+
+          If you're not intentionally resetting your local test_data database to an earlier
+          version, you may want to take a closer look before taking any destructive actions.
+
+        MSG
+      end
+    end
+  end
+end

data/lib/test_data/warns_if_dump_is_newer_than_database.rb

@@ -0,0 +1,36 @@
+module TestData
+  class WarnsIfDumpIsNewerThanDatabase
+    def initialize
+      @config = TestData.config
+      @determines_when_sql_dump_was_made = DeterminesWhenSqlDumpWasMade.new
+      @determines_databases_associated_dump_time = DeterminesDatabasesAssociatedDumpTime.new
+    end
+
+    def call
+      return unless Rails.env.test_data?
+      sql_dumped_at = @determines_when_sql_dump_was_made.call
+      database_dumped_at = @determines_databases_associated_dump_time.call
+
+      if sql_dumped_at.present? &&
+          database_dumped_at.present? &&
+          sql_dumped_at > database_dumped_at
+        TestData.log.warn <<~MSG
+          The SQL dumps in '#{File.dirname(@config.data_dump_path)}' were created
+          after your local test_data database '#{@config.database_name}' was last dumped.
+
+            SQL Dump: #{sql_dumped_at.localtime}
+            Database: #{database_dumped_at.localtime}
+
+          To avoid potential data loss, you may want to consider dropping '#{@config.database_name}'
+          and loading the SQL dumps before making changes to the test data in this database
+          or performing another dump.
+
+          To do this, kill any processes with RAILS_ENV=test_data and then run:
+
+            $ bin/rake test_data:reinitialize
+
+        MSG
+      end
+    end
+  end
+end

data/lib/test_data.rb

@@ -12,20 +12,26 @@ require_relative "test_data/configurators/webpacker_yaml"
 require_relative "test_data/custom_loaders/abstract_base"
 require_relative "test_data/custom_loaders/rails_fixtures"
 require_relative "test_data/detects_database_emptiness"
+require_relative "test_data/detects_database_existence"
+require_relative "test_data/determines_when_sql_dump_was_made"
+require_relative "test_data/determines_databases_associated_dump_time"
 require_relative "test_data/dumps_database"
 require_relative "test_data/error"
 require_relative "test_data/inserts_test_data"
 require_relative "test_data/installs_configuration"
 require_relative "test_data/loads_database_dumps"
 require_relative "test_data/log"
+require_relative "test_data/manager"
 require_relative "test_data/railtie"
+require_relative "test_data/records_dump_metadata"
 require_relative "test_data/save_point"
 require_relative "test_data/statistics"
-require_relative "test_data/manager"
 require_relative "test_data/truncates_test_data"
 require_relative "test_data/verifies_configuration"
 require_relative "test_data/verifies_dumps_are_loadable"
 require_relative "test_data/version"
+require_relative "test_data/warns_if_dump_is_newer_than_database"
+require_relative "test_data/warns_if_database_is_newer_than_dump"
 require_relative "generators/test_data/environment_file_generator"
 require_relative "generators/test_data/initializer_generator"
 require_relative "generators/test_data/cable_yaml_generator"
@@ -37,25 +43,30 @@ module TestData
   def self.uninitialize
     @manager ||= Manager.new
     @manager.rollback_to_before_data_load
+    nil
   end
 
   def self.uses_test_data
     @manager ||= Manager.new
     @manager.load
+    nil
   end
 
   def self.uses_clean_slate
     @manager ||= Manager.new
     @manager.truncate
+    nil
   end
 
   def self.uses_rails_fixtures(test_instance)
     @rails_fixtures_loader ||= CustomLoaders::RailsFixtures.new
     @manager ||= Manager.new
     @manager.load_custom_data(@rails_fixtures_loader, test_instance: test_instance)
+    nil
   end
 
   def self.insert_test_data_dump
     InsertsTestData.new.call
+    nil
   end
 end

data/script/test

@@ -28,11 +28,45 @@ bin/rails test test/integration/better_mode_switching_demo_test.rb
 bin/rails test test/integration/parallel_boops_with_fixtures_test.rb
 bin/rails test test/integration/parallel_boops_without_fixtures_test.rb
 
+# Verify the out-of-date database warning system works (step 1)
+mkdir -p tmp/dump-backup-1
+cp test/support/test_data/* tmp/dump-backup-1
+
 # Test using the test_data env to interactively create test data
 RAILS_ENV=test_data rails runner "5.times { Boop.create! }"
 bin/rake test_data:dump
 bin/rails test test/integration/updated_boops_test.rb
 
+# Verify the out-of-date database warning system works (step 2)
+mkdir -p tmp/dump-backup-2
+cp test/support/test_data/* tmp/dump-backup-2
+cp tmp/dump-backup-1/* test/support/test_data
+set +e
+result=`yes "n" | bin/rake test_data:reinitialize 2>&1`
+set -e
+if ! echo "$result" | grep -q "\[test_data:warn\] Your local test_data database 'example_test_data' is associated"; then
+  echo "Expected to be warned that the SQL dump was older than the database, but there was no warning."
+  exit 1
+fi
+TEST_DATA_CONFIRM=true bin/rake test_data:reinitialize
+cp tmp/dump-backup-2/* test/support/test_data
+if ! RAILS_ENV=test_data bin/rails runner "" 2>&1 | grep -q "\[test_data:warn\] The SQL dumps in 'test/support/test_data' were created"; then
+  echo "Expected to be warned that the SQL dump was newer than the database, but there was no warning."
+  exit 1
+fi
+set +e
+result=`yes "n" | bin/rake test_data:reinitialize 2>&1`
+set -e
+if echo "$result" | grep -q "\[test_data:warn\] Your local test_data database 'example_test_data' is associated"; then
+  echo "Expected NOT to be warned that the SQL dump was older than the database, but a warning was printed."
+  exit 1
+fi
+TEST_DATA_CONFIRM=true bin/rake test_data:reinitialize
+if RAILS_ENV=test_data bin/rails runner "" 2>&1 | grep -q "\[test_data:warn\]"; then
+  echo "Expected NOT to be warned that the SQL dump was newer than the database, but a warning was printed."
+  exit 1
+fi
+
 # Test a migration being added and run and an out-of-date dump being loaded
 cp ../test/fixtures/20210418220133_add_beep_to_boops.rb db/migrate
 cp ../test/fixtures/20210624180810_create_pants.rb db/migrate

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: test_data
 version: !ruby/object:Gem::Version
-  version: 0.2.2
+  version: 0.3.0
 platform: ruby
 authors:
 - Justin Searls
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2021-08-03 00:00:00.000000000 Z
+date: 2021-09-13 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: railties
@@ -136,6 +136,9 @@ files:
 - lib/test_data/custom_loaders/abstract_base.rb
 - lib/test_data/custom_loaders/rails_fixtures.rb
 - lib/test_data/detects_database_emptiness.rb
+- lib/test_data/detects_database_existence.rb
+- lib/test_data/determines_databases_associated_dump_time.rb
+- lib/test_data/determines_when_sql_dump_was_made.rb
 - lib/test_data/dumps_database.rb
 - lib/test_data/error.rb
 - lib/test_data/generator_support.rb
@@ -146,12 +149,15 @@ files:
 - lib/test_data/manager.rb
 - lib/test_data/railtie.rb
 - lib/test_data/rake.rb
+- lib/test_data/records_dump_metadata.rb
 - lib/test_data/save_point.rb
 - lib/test_data/statistics.rb
 - lib/test_data/truncates_test_data.rb
 - lib/test_data/verifies_configuration.rb
 - lib/test_data/verifies_dumps_are_loadable.rb
 - lib/test_data/version.rb
+- lib/test_data/warns_if_database_is_newer_than_dump.rb
+- lib/test_data/warns_if_dump_is_newer_than_database.rb
 - script/reset_example_app
 - script/test
 - test_data.gemspec