Fix the test that was broken by #16445 rather than deleting it

Since the counter cache was properly being updated, the model became
stale. Simply reloading the model before attempting to destroy is
sufficient for this case. I believe this is enough of an edge case to be
a valid change to the tests, even though it represents a potential
breaking change.

1 files changed, 12 insertions, 0 deletions

diff --git a/activerecord/test/cases/locking_test.rb b/activerecord/test/cases/locking_test.rb
index 839bbea5bb..2e1363334d 100644
--- a/activerecord/test/cases/locking_test.rb
+++ b/activerecord/test/cases/locking_test.rb
@@ -263,6 +263,18 @@ class OptimisticLockingTest < ActiveRecord::TestCase
     end
   end
 
+  def test_polymorphic_destroy_with_dependencies_and_lock_version
+    car = Car.create!
+
+    assert_difference 'car.wheels.count'  do
+      car.wheels << Wheel.create!
+    end
+    assert_difference 'car.wheels.count', -1  do
+      car.reload.destroy
+    end
+    assert car.destroyed?
+  end
+
   def test_removing_has_and_belongs_to_many_associations_upon_destroy
     p = RichPerson.create! first_name: 'Jon'
     p.treasures.create!