assertNotNull(clazz.getMethod("getName"), "Should have getName method");
            assertNotNull(clazz.getMethod("getType"), "Should have getType method");
            assertNotNull(clazz.getMethod("exists"), "Should have exists method");
            assertNotNull(clazz.getMethod("resolve", String.class), "Should have resolve method");
            assertNotNull(clazz.getMethod("close"), "Should have close method");
        }

    }

    /**
     * Test that methods are properly overridden
     */
    @Test
    @DisplayName("Test methods are properly overridden from parent class")
    public void testMethodOverrides() throws NoSuchMethodException {
        // Given
        Class<?> clazz = SmbComTreeDisconnect.class;

        // When & Then - verify methods are declared in this class (overridden)

 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 */

package jcifs.internal.util;

/**
 * Utility class providing string manipulation methods for the jCIFS library.
 * Contains helper methods for string operations, including backported JDK functionality
 * for compatibility with older Java versions.
 */
public final class StringUtil {

    /**
     *
     */

 * callers. Instead, accept {@link Iterable} and have your method or constructor body pass it to the
 * appropriate {@code copyOf} method itself.
 *
 * <p>Expressing the immutability guarantee directly in the type that user code references is a
 * powerful advantage. Although Java offers certain immutable collection factory methods, such as
 * {@link Collections#singleton(Object)} and <a

  protected ForwardingObject() {}

  /**
   * Returns the backing delegate instance that methods are forwarded to. Abstract subclasses
   * generally override this method with an abstract method that has a more specific return type,
   * such as {@link ForwardingSet#delegate}. Concrete subclasses override this method to supply the
   * instance being decorated.
   */
  protected abstract Object delegate();

        // Then
        assertTrue(CommonServerMessageBlockRequest.class.isAssignableFrom(Request.class));
    }

    @Test
    @DisplayName("Test Request methods inherited from CommonServerMessageBlockRequest")
    void testInheritedMethods() {
        // Given
        when(request.isResponseAsync()).thenReturn(true);
        when(request.getNext()).thenReturn(nextRequest);

 *       String}.
 * </ul>
 *
 * This is the same behavior as type-variable usages have to Kotlin and to the Checker Framework.
 * Contrast the method above to:
 *
 * <ul>
 *   <li>methods whose return type is a type variable but which can never return {@code null},
 *       typically because the type forbids nullable type arguments: For example, {@code

 *       String}.
 * </ul>
 *
 * This is the same behavior as type-variable usages have to Kotlin and to the Checker Framework.
 * Contrast the method above to:
 *
 * <ul>
 *   <li>methods whose return type is a type variable but which can never return {@code null},
 *       typically because the type forbids nullable type arguments: For example, {@code

import org.jspecify.annotations.Nullable;

/**
 * An extension of {@code DataInput} for reading from in-memory byte arrays; its methods offer
 * identical functionality but do not throw {@link IOException}.
 *
 * <p><b>Warning:</b> The caller is responsible for not attempting to read past the end of the
 * array. If any method encounters the end of the array prematurely, it throws {@link

 * to implement the related methods as well. Finally, two collection views are provided: {@link
 * #elementSet} contains the distinct elements of the multiset "with duplicates collapsed", and
 * {@link #entrySet} is similar but contains {@link Entry Multiset.Entry} instances, each providing
 * both a distinct element and the count of that element.
 *
 * <p>In addition to these required methods, implementations of {@code Multiset} are expected to