@DisplayName("String ctor: preserves message; default unsuccessful status")
    void messageConstructor_handlesNullAndEmpty(String msg) {
        // Act
        SmbAuthException ex = new SmbAuthException(msg);

        // Assert
        assertEquals(msg, ex.getMessage());
        assertEquals(NtStatus.NT_STATUS_UNSUCCESSFUL, ex.getNtStatus(), "default status must be unsuccessful");
        assertNull(ex.getCause());

    }

    // Happy path: message + cause constructor should chain cause and set unsuccessful status
    @ParameterizedTest
    @NullSource
    @ValueSource(strings = { "", "error", "detailed message" })
    @DisplayName("Message+Cause ctor: propagates message/cause and unsuccessful status")

        // Assert
        assertEquals("Unexpectedly reached end of file", ex.getMessage(), "Default message must match");
        assertEquals(NtStatus.NT_STATUS_UNSUCCESSFUL, ex.getNtStatus(), "Default NT status should be UNSUCCESSFUL");
        assertNull(ex.getCause(), "Cause should be null by default");
        assertNull(ex.getRootCause(), "Root cause should be null by default");

     * @param extraPad
     *            extra padding to include in signature
     * @param msg
     *            The message to verify
     * @return whether verification was unsuccessful
     */
    boolean verify(byte[] data, int offset, int length, int extraPad, CommonServerMessageBlock msg);

 * </p>
 *
 * <p>
 * It handles successful responses by transforming the data using a {@link Transformer}
 * and storing the result. It also handles "Not Modified" responses by creating an empty
 * result and storing it. Unsuccessful responses are logged for debugging purposes.
 * </p>
 *
 * <p>
 * The class uses {@link CrawlerContainer} to access components like {@link AccessResult}

    int NT_STATUS_NOTIFY_ENUM_DIR = 0x0000010C;
    /** The data was too large to fit into the specified buffer */
    int NT_STATUS_BUFFER_OVERFLOW = 0x80000005;
    /** The requested operation was unsuccessful */
    int NT_STATUS_UNSUCCESSFUL = 0xC0000001;
    /** The requested operation is not implemented */
    int NT_STATUS_NOT_IMPLEMENTED = 0xC0000002;
    /** The specified information class is invalid */

     * block is automatically generated from the ntstatus package.
     */

    /** The operation completed successfully */
    int NT_STATUS_SUCCESS = 0x00000000;
    /** The requested operation was unsuccessful */
    int NT_STATUS_UNSUCCESSFUL = 0xC0000001;
    /** The requested operation is not implemented */
    int NT_STATUS_NOT_IMPLEMENTED = 0xC0000002;
    /** The specified information class is invalid */

</p>

<p class="rule">
A successful call to <code>l.TryLock</code> (or <code>l.TryRLock</code>)
is equivalent to a call to <code>l.Lock</code> (or <code>l.RLock</code>).
An unsuccessful call has no synchronizing effect at all.
As far as the memory model is concerned,
<code>l.TryLock</code> (or <code>l.TryRLock</code>)
may be considered to be able to return false
even when the mutex <i>l</i> is unlocked.

        </field>
        <field>
          <name>notifiers</name>
          <version>4.0.0+</version>
          <description>Configuration for notifying developers/users when a build is unsuccessful,
            including user information and notification mode.</description>
          <association>
            <multiplicity>*</multiplicity>
            <type>Notifier</type>
          </association>