Skip mutation testing AsyncRecord.

AsyncRecord follows ActiveRecord API with regard to after_commit
callbacks.

This API has changed over releases we still support (4, 5,
6). Some of AsyncRecord record methods will not be called in some
ActiveRecord versions, yet mutant expects to remove those.

Introducing release-specific AsyncRecord class could have been the solution
but there will still be dead code from mutant perspective, that is all
classes not needed under current ActiveRecord version.

It does not seem to be the hill worth dying on.

rails_event_store/Makefile

@@ -2,7 +2,8 @@ GEM_VERSION = $(shell cat ../RES_VERSION)
 GEM_NAME    = rails_event_store
 REQUIRE     = $(GEM_NAME)
 IGNORE      = RailsEventStore::Client\#initialize \
-              RailsEventStore::AfterCommitAsyncDispatcher::AsyncRecord\#rolledback!
+              RailsEventStore::AfterCommitAsyncDispatcher::AsyncRecord* \
+              RailsEventStore::AfterCommitAsyncDispatcher\#async_record
 SUBJECT      ?= RailsEventStore*
 DATABASE_URL ?= sqlite3::memory:
 

rails_event_store/lib/rails_event_store/after_commit_async_dispatcher.rb

@@ -16,14 +16,16 @@ def run(&schedule_proc)
       transaction = ActiveRecord::Base.connection.current_transaction
 
       if transaction.joinable?
-        transaction.add_record(
-          AsyncRecord.new(self, schedule_proc)
-        )
+        transaction.add_record(async_record(schedule_proc))
       else
         yield
       end
     end
 
+    def async_record(schedule_proc)
+      AsyncRecord.new(self, schedule_proc)
+    end
+
     def verify(subscriber)
       @scheduler.verify(subscriber)
     end