Subject first = orig.getSubject();
        // In test environments, getSubject() may return null if JAAS is not configured
        // This is acceptable behavior - the test should focus on the cloning logic

        // Clone and verify basic fields copied
        JAASAuthenticator copy = (JAASAuthenticator) orig.clone();

   * escaping for code points if required.
   *
   * <p>Note that arrays returned by this method must not be modified once they have been returned.
   * However it is acceptable to return the same array multiple times (even for different input
   * characters).
   *
   * @param cp the Unicode code point to escape
   * @return the replacement characters, or {@code null} if no escaping was required

   * characters unescaped, they would be escaped by the consumer at parse time, anyway.</a>)
   * Additionally, the escaper escapes the slash character ("/"). While slashes are acceptable in
   * URL paths, they are considered by the specification to be separators between "path segments."
   * This implies that, if you wish for your path to contain slashes, you must escape each segment

   * generalized escaping for characters.
   *
   * <p>Note that arrays returned by this method must not be modified once they have been returned.
   * However it is acceptable to return the same array multiple times (even for different input
   * characters).
   *
   * @param c the character to escape
   * @return the replacement characters, or {@code null} if no escaping was required
   */

        } catch (final RuntimeException e) {
            // POI may throw IllegalArgumentException or other RuntimeExceptions
            // for invalid data, which is also acceptable
            assertNotNull("Exception message should not be null", e.getMessage());
        }
    }

    /**
     * Test that MsExcelExtractor throws appropriate exception for invalid data.

        boolean deletionFailed = false;
        try {
            dirToDelete.delete();
            // Some SMB implementations may allow this, which is non-standard but acceptable for testing
            log.info("Non-empty directory deletion succeeded (non-standard behavior, but acceptable in Docker/Samba)");
        } catch (SmbException e) {
            // This is the expected behavior per SMB specification
            deletionFailed = true;

        verify(filter).accept(resource);
        verify(resource).close();
    }

    @Test
    @DisplayName("Iterator with rejecting filter - finds next acceptable")
    void iteratorWithRejectingFilter() throws Exception {
        // Setup: first entry rejected, second accepted
        FileEntry entry1 = mock(FileEntry.class);
        FileEntry entry2 = mock(FileEntry.class);

   * characters unescaped, they would be escaped by the consumer at parse time, anyway.</a>)
   * Additionally, the escaper escapes the slash character ("/"). While slashes are acceptable in
   * URL paths, they are considered by the specification to be separators between "path segments."
   * This implies that, if you wish for your path to contain slashes, you must escape each segment

        // Destroy the storage - may throw DestroyFailedException if SecretKey doesn't support destroy
        try {
            storage.destroy();
        } catch (DestroyFailedException e) {
            // This is acceptable - not all JVM implementations support destroying SecretKey
            // The important part is that the storage is marked as destroyed
        }

        // Given
        byte[] buffer = new byte[256];

        // Write structure size (4)
        SMBUtil.writeInt2(4, buffer, 0);
        // Write reserved field (any value is acceptable)
        buffer[2] = (byte) byte2;
        buffer[3] = (byte) byte3;

        // When
        int bytesRead = response.readBytesWireFormat(buffer, 0);