From 03f7efc8463569c27dc6b03b535ed25fe7594ff8 Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Mon, 18 Mar 2024 14:11:28 -0600
Subject: [PATCH] Change comment

---
 src/epplibwrapper/tests/test_client.py | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/src/epplibwrapper/tests/test_client.py b/src/epplibwrapper/tests/test_client.py
index 3671ea5b9..b623b44e0 100644
--- a/src/epplibwrapper/tests/test_client.py
+++ b/src/epplibwrapper/tests/test_client.py
@@ -264,11 +264,17 @@ class TestClient(TestCase):
             self.assertEquals(mock_send.call_count, 5)
 
     def test_send_command_close_failure_recovers(self):
-        """Test when the .close on a connection fails and a .send follows suit.
+        """
+        Validates the resilience of the connection handling mechanism 
+        during command execution on retry.
+        
         Scenario:
-        Initialization succeeds
-        Send command fails (with 2400 code) prompting retry
-        Client closes and re-initializes, and command succeeds"""
+        - Initialization of the connection is successful.
+        - An attempt to send a command fails with a specific error code (ConcurrentObjectUseError)
+        - The client attempts to retry.
+        - Subsequently, the client re-initializes the connection.
+        - A retry of the command execution post-reinitialization succeeds.
+        """
 
         expected_result = self.get_fake_epp_result()
         wrapper = None