assertNotNull(logonInfo.getGroupSids());
        assertNotNull(logonInfo.getExtraSids());
        assertNotNull(logonInfo.getResourceGroupSids());

        // Verify mock interactions
        verify(logonInfo).getUserName();
        verify(logonInfo).getDomainName();
        verify(logonInfo).getServerName();
    }

    @Test
    @DisplayName("Test date conversion from FILETIME")

        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, "..");

            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 {

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;

variables from your model are also going to be untrusted. That means that if
your code interacts with the filesystem, network, etc. and uses checkpointed
variables as part of those interactions (ex: using a string variable to build a
filesystem path), a maliciously created checkpoint might be able to change the
targets of those operations, which could result in arbitrary
read/write/executions.

    @Mock
    private ServletOutputStream servletOutputStream;

    @BeforeEach
    void setUp() throws Exception {
        filter = new NtlmHttpFilter();

        // Setup lenient stubs for common mock interactions
        lenient().when(request.getSession()).thenReturn(httpSession);
        lenient().when(request.getSession(anyBoolean())).thenReturn(httpSession);

        assertFalse(it.hasNext(), "Iterator should be exhausted");

        // Close explicitly to exercise doCloseInternal
        it.close();

        // Verify interactions: one create, two additional directory queries (for fetchMore), one close
        verify(tree, times(1)).send(argThat((Request<?> r) -> r instanceof Smb2CreateRequest));

import org.jspecify.annotations.Nullable;

/**
 * A helper for concurrency testing. One or more {@code TestThread} instances are instantiated in a
 * test with reference to the same "lock-like object", and then their interactions with that object
 * are choreographed via the various methods on this class.
 *
 * <p>A "lock-like object" is really any object that may be used for concurrency control. If the

        when(config.isIpcSigningEnforced()).thenReturn(true);
        when(creds.isAnonymous()).thenReturn(true);
        assertFalse(ipc.shouldForceSigning());

        // Verify interactions sequence for one call
        InOrder inOrder = inOrder(config, creds);
        ipc = locator("smb://server/IPC$/");
        ipc.shouldForceSigning();
        inOrder.verify(config, atLeastOnce()).isIpcSigningEnforced();

    assertFalse("stopAsync has deadlocked!.", stoppingThread.isAlive());
    failLeave.countDown(); // release the background thread
  }

  /**
   * Catches a bug where when constructing a service manager failed, later interactions with the
   * service could cause IllegalStateExceptions inside the partially constructed ServiceManager.
   * This ISE wouldn't actually bubble up but would get logged by ExecutionQueue. This obfuscated