able to run tests in parallel

.rspec_parallel

@@ -0,0 +1,2 @@
+--format progress
+--format ParallelTests::RSpec::RuntimeLogger --out tmp/parallel_runtime_rspec.log

Gemfile

@@ -68,6 +68,8 @@ group :development, :test do
   gem "byebug", platforms: %i[mri mingw x64_mingw]
   gem "dotenv-rails"
   gem "pry-byebug"
+
+  gem "parallel_tests"
 end
 
 group :development do

Gemfile.lock

@@ -247,6 +247,8 @@ GEM
       globalid
       paper_trail (>= 3.0.0)
     parallel (1.22.1)
+    parallel_tests (4.0.0)
+      parallel
     parser (3.1.2.1)
       ast (~> 2.4.1)
     pg (1.4.3)
@@ -430,6 +432,7 @@ PLATFORMS
   x86_64-darwin-19
   x86_64-darwin-20
   x86_64-darwin-21
+  x86_64-darwin-22
   x86_64-linux
 
 DEPENDENCIES
@@ -456,6 +459,7 @@ DEPENDENCIES
   overcommit (>= 0.37.0)
   paper_trail
   paper_trail-globalid
+  parallel_tests
   pg (~> 1.1)
   possessive
   postcodes_io

config/database.yml

@@ -66,7 +66,7 @@ staging:
 # Do not set this db to the same as development or production.
 test:
   <<: *default
-  database: data_collector_test
+  database: data_collector_test<%= ENV['TEST_ENV_NUMBER'] %>
 
 # As with config/credentials.yml, you never want to store sensitive information,
 # like your database password, in your source code. If your source code is

config/environments/test.rb

@@ -1,4 +1,5 @@
 require "active_support/core_ext/integer/time"
+require "faker"
 
 # The test environment is used exclusively to run your application's
 # test suite. You never need to work with it otherwise. Remember that