}

    @Test
    @DisplayName("constructor accepts null principal")
    void testConstructorWithNullPrincipal(@Mock HttpServletRequest mockRequest) {
        // Constructor accepts null principal without throwing exception
        NtlmHttpServletRequest request = new NtlmHttpServletRequest(mockRequest, null);

        // getRemoteUser() will throw NPE when trying to call getName() on null principal

    SomeCheckedException cause = new SomeCheckedException();
    SomeChainingException thrown = new SomeChainingException(cause);

    assertThat(thrown).hasCauseThat().isSameInstanceAs(cause);
    assertThat(getCauseAs(thrown, SomeCheckedException.class)).isSameInstanceAs(cause);
    assertThat(getCauseAs(thrown, Exception.class)).isSameInstanceAs(cause);

    ClassCastException expected =
        assertThrows(

     * during the Maven build lifecycle to perform the Mojo's designated task.
     *
     * <p>Implementations should handle any task-specific logic and may communicate
     * errors by throwing an {@link Exception}. Error conditions should provide
     * sufficient detail to aid troubleshooting.</p>
     *
     * @throws Exception if any issue occurs that prevents the successful execution

        assertTrue(exception instanceof Exception);
        assertTrue(exception instanceof Throwable);
    }

    public void test_throwAndCatch() {
        // Test throwing and catching the exception
        try {
            throw new DictionaryExpiredException();
        } catch (DictionaryExpiredException e) {
            assertNotNull(e);
            assertNull(e.getMessage());

        // Assert
        assertFalse(it.hasNext(), "No next when opened with null initial");
        verify(tree, times(1)).release(); // closed in constructor
    }

    @Test
    @DisplayName("open() throwing CIFSException triggers close and rethrow")
    void constructorOpenThrows() {
        // Arrange
        stubAcquireReturnsSelf();

 * second invocation, so implementors have made various choices, including:
 *
 * <ul>
 *   <li>returning the same iterator again
 *   <li>throwing an exception of some kind
 *   <li>or the usual, <i>robust</i> behavior, which all known {@link Collection} implementations
 *       have, of returning a new, independent iterator
 * </ul>
 *

 * <p>
 * The class under test is a simple wrapper around the base class that
 * sets internal fields in its constructor.
 * These tests verify that the constructor accepts various parameters
 * without throwing exceptions.
 */
@ExtendWith(MockitoExtension.class)
class MsrpcSamrConnect2Test {

    // Helper method to create a minimal SamrPolicyHandle instance.
    private static SamrPolicyHandle createMockPolicyHandle() {

        assertNotNull(exception);
        assertEquals(longMessage, exception.getMessage());
    }

    public void test_throwAndCatch() {
        // Test throwing and catching the exception
        String expectedMessage = "Theme loading error";

        try {
            throw new ThemeException(expectedMessage);
        } catch (ThemeException e) {

     * specified by the <code>UniAddress</code> parameter. If the credentials are
     * not accepted, an <code>SmbAuthException</code> will be thrown. If an error
     * occurs an <code>SmbException</code> will be thrown. If the credentials are
     * valid, the method will return without throwing an exception. See the
     * last <a href="../../../faq.html">FAQ</a> question.
     * <p>

        assertEquals(rootCause, exception.getCause().getCause());
        assertEquals("Root cause", exception.getCause().getCause().getMessage());
    }

    public void test_throwAndCatch() {
        // Test throwing and catching the exception
        String expectedMessage = "Job execution failed";
        boolean exceptionCaught = false;

        try {
            throw new ScheduledJobException(expectedMessage);