assertEquals("b", it.next().getName());
        assertTrue(it.hasNext());
        assertEquals("c", it.next().getName());
        assertFalse(it.hasNext());

        // Verify interactions
        verify(tree, times(1)).send(isA(Trans2FindFirst2.class), any(Trans2FindFirst2Response.class));
        // Verify that Trans2FindNext2 was sent twice for fetching more entries

import org.mockito.junit.jupiter.MockitoExtension;

import jcifs.SmbSession;

/**
 * Tests for SmbTransportInternal interface using Mockito mocks to
 * exercise method contracts, checked exceptions, and interactions.
 */
@ExtendWith(MockitoExtension.class)
public class SmbTransportInternalTest {

    @Mock
    private SmbTransportInternal transport;

    @Mock
    private jcifs.CIFSContext ctx;

    @Mock

        assertTrue(r.getName().startsWith("OKSERVER"), "Expected valid entry to be adapted");
        assertFalse(itr.hasNext());
    }

    @Test
    @DisplayName("Filter rejects first, accepts second; interactions verified")
    void filterRejectsThenAccepts_nextYieldsAccepted() throws Exception {
        // Arrange: two entries; filter rejects first, accepts second
        setupParentForUrlCreation();

        void shouldHandleResponseMapOperations() {
            assertEquals(0, transport.getResponseMapSize());
            // Response map is accessible through protected field for testing
            // but we avoid complex interactions here for performance
        }
    }

            assertNotEquals(a, b);
            assertNotEquals(a, c);
            assertNotEquals(a, new Object());
        }
    }

    @Test
    @DisplayName("Mockito presence: no collaborator interactions to verify")
    void noDependenciesToMock() {
        // This class has no external collaborators; nothing to verify.
        // Keep Mockito import usage minimal to satisfy build-time linkage.

* services
* injectables
* components

## **FastAPI** plug-ins { #fastapi-plug-ins }

Integrations and "plug-ins" can be built using the **Dependency Injection** system. But in fact, there is actually **no need to create "plug-ins"**, as by using dependencies it's possible to declare an infinite number of integrations and interactions that become available to your *path operation functions*.

        byte[] out = ctx.initSecContext(null, 0, 0);

        // Assert: returns a SPNEGO token (opaque here but non-null/non-empty)
        assertNotNull(out);
        assertTrue(out.length > 0);

        // Verify interactions: flags and an empty optimistic token are used
        verify(this.mechContext, times(1)).getFlags();
        ArgumentCaptor<byte[]> cap = ArgumentCaptor.forClass(byte[].class);

        assertNotNull(e2);
        assertEquals("first", e1.getName());
        assertEquals(acceptedName, e2.getName(), "Should return the first name accepted by filter");

        // Verify filter interactions: not called for '.' and '..', called for others
        verify(nameFilter, never()).accept(parent, ".");
        verify(nameFilter, never()).accept(parent, "..");

import jcifs.internal.NotifyResponse;
import jcifs.internal.smb1.trans.nt.NtTransNotifyChange;
import jcifs.internal.smb2.notify.Smb2ChangeNotifyRequest;

/**
 * Tests for SmbWatchHandleImpl focusing on behavior and interactions.
 */
@ExtendWith(MockitoExtension.class)
class SmbWatchHandleImplTest {

    @Mock
    SmbFileHandleImpl handle;

    @Mock
    SmbTreeHandleImpl tree;

            assertEquals(0, in.skip(0));
            assertEquals(0, in.skip(-1));
            assertEquals(5, in.skip(5));
        }
    }

    @Nested
    @DisplayName("SMB1 interactions")
    class Smb1Behavior {

        @Test
        @DisplayName("Named pipe: broken pipe maps to -1")
        void namedPipeBrokenPipeReturnsMinusOne() throws Exception {