You will see the automatic API docs for the sub-application, including only its own _path operations_, all under the correct sub-path prefix `/subapi`:

<img src="/img/tutorial/sub-applications/image02.png">

If you try interacting with any of the two user interfaces, they will work correctly, because the browser will be able to talk to each specific app or sub-app.

### Technical Details: `root_path` { #technical-details-root-path }

### Documentação automática { #automatic-docs }

Documentação interativa da API e navegação web da interface de usuário. Como o framework é baseado no OpenAPI, há várias opções, 2 incluídas por padrão.

* <a href="https://github.com/swagger-api/swagger-ui" class="external-link" target="_blank"><strong>Swagger UI</strong></a>, com navegação interativa, chame e teste sua API diretamente do navegador.

        assertThrows(ArrayIndexOutOfBoundsException.class, () -> {
            @SuppressWarnings("unused")
            String s = msgs[msgs.length];
        });
    }

    @Test
    @DisplayName("Interaction: consumer is invoked for each found mapping")
    void interactionWithConsumerIsAsExpected() {
        // Arrange: choose a small set of known DOS codes

    protected Executor executor() {
      transitionStates.add(state());
      return directExecutor();
    }
  }

  // Functional tests using real thread. We only verify publicly visible state.
  // Interaction assertions are done by the single-threaded unit tests.

  private static class DefaultService extends AbstractIdleService {
    @Override
    protected void startUp() throws Exception {}

    @Override

                Arguments.of(-1, -2L, -3L, -4L, -5L) // negative values
        );
    }

    // --- Mockito interaction: verify each getter is invoked and returns stubbed values ---
    @Test
    void mockitoMock_verifiesGetterInteractions() {
        // Arrange: mock and stub each getter with distinct values

 * methods (writing parameters and handling empty wire formats) and an
 * informative {@link NtTransQuerySecurityDesc#toString()}. The tests
 * exercise normal behaviour, boundary values, and the interaction with
 * the underlying wire‑format helpers.
 */
@ExtendWith(MockitoExtension.class)
class NtTransQuerySecurityDescTest {

    /**
     * Helper that mimics the write logic used by

        assertEquals(NtStatus.NT_STATUS_UNSUCCESSFUL, ex.getNtStatus(), "Status should default to unsuccessful for message+cause ctor");
    }

    // Interaction: passing a mocked cause should not trigger interactions (nothing to call)
    @Test
    @DisplayName("Mocked cause: no interactions occur when stored as cause")
    void mockedCause_isStored_withoutInteraction() {

import org.mockito.junit.jupiter.MockitoExtension;

/**
 * Unit tests for {@link NdrShort}.  The tests cover construction,
 * encoding and decoding logic, masking behaviour, alignment handling and
 * interaction with {@link NdrBuffer}.  All public behaviour is exercised.
 */
@ExtendWith(MockitoExtension.class)
class NdrShortTest {

    /**
     * A small reusable buffer for encode/decode tests.
     */

            assertEquals("server/", root.getName());
        }
    }

    @Mock
    DfsReferralData dfs;
    @Mock
    Address addr;

    @Test
    @DisplayName("Mockito interaction – dependent objects are called appropriately")
    void testInteractionsWithStubbedDependencies() throws Exception {
        String url = "smb://server/share/";

        assertEquals("boom", ex.getMessage(), "Exception message should be preserved");
        verifyNoInteractions(mockDir);
    }

    /**
     * Interaction with dependency: implementation can use directory's methods to make decisions.
     * Tests a filter that uses directory path information.
     */
    @Test