v2.0.x Chores (3) - for `tests/test_exceptions.py`

[reactive-firewall]

49-60: Consider enhancing class documentation with test coverage information

While the docstring is well-written, it could be more comprehensive by:

1. Mentioning both CommandExecutionError and ShutdownCommandReceived test coverage
2. Documenting the test strategy for different initialization scenarios
3. Explaining the relationship with BasicUsageTestSuite

 class ExceptionsTestSuite(BasicUsageTestSuite):
     """
     Test suite for validating the behavior of exception classes in the multicast package.
 
-    This suite focuses on testing the CommandExecutionError class, verifying its
-    initialization with different arguments and proper error propagation.
+    This suite comprehensively tests both CommandExecutionError and ShutdownCommandReceived
+    classes, verifying:
+    - Initialization with various argument combinations
+    - Default values and overrides
+    - Exception chaining and cause propagation
+    - Exit code handling and constraints
+
+    The suite extends BasicUsageTestSuite to leverage common test infrastructure
+    and maintain consistency across the test framework.
     """

---

61-94: Consider adding negative test cases for CommandExecutionError

The current test coverage for CommandExecutionError is thorough for valid inputs, but could be enhanced by testing:

1. Invalid exit codes (negative or non-integer values)
2. None or empty message scenarios
3. Invalid cause types

Example test method to add:

def test_command_execution_error_with_invalid_inputs(self):
    """Test CommandExecutionError handling of invalid inputs.

    Verifies that the class properly handles edge cases and invalid inputs
    by either raising appropriate exceptions or applying sensible defaults.
    """
    # Test with invalid exit code
    with self.assertRaises(ValueError):
        multicast.exceptions.CommandExecutionError("Test", -1)
    
    # Test with None message
    error = multicast.exceptions.CommandExecutionError(None)
    self.assertIsNotNone(error.message)
    
    # Test with invalid cause type
    with self.assertRaises(TypeError):
        multicast.exceptions.CommandExecutionError(42, "Test")  # number as cause

---

95-140: Consider using parameterized tests for ShutdownCommandReceived

The test cases for ShutdownCommandReceived are comprehensive but could be more maintainable using parameterized tests. This would make it easier to add new test cases and reduce code duplication.

Example using unittest.TestCase.subTest:

def test_shutdown_received_error_scenarios(self):
    """Test ShutdownCommandReceived across multiple scenarios using parameterized tests."""
    test_cases = [
        {
            'name': 'custom_message',
            'args': ("Test Shutdown",),
            'expected': {'message': "Test Shutdown", 'exit_code': 143}
        },
        {
            'name': 'with_exit_code_override_attempt',
            'args': ("Test Shutdown", 42),
            'expected': {'message': "Test Shutdown", 'exit_code': 143}
        },
        {
            'name': 'no_args',
            'args': tuple(),
            'expected': {'message': "SHUTDOWN", 'exit_code': 143}
        }
    ]
    
    for case in test_cases:
        with self.subTest(name=case['name']):
            error = multicast.exceptions.ShutdownCommandReceived(*case['args'])
            self.assertEqual(error.message, case['expected']['message'])
            self.assertEqual(error.exit_code, case['expected']['exit_code'])