Todas as declarações de requisições, validações e requisitos para suas dependências (e sub-dependências) serão integradas em um mesmo esquema OpenAPI.

Então, a documentação interativa também terá toda a informação sobre essas dependências:

<img src="/img/tutorial/dependencies/image01.png">

## Caso de Uso Simples { #simple-usage }

                cwd,
                userHome,
                List.of("eu.maveniverse.maven.plugins:toolbox:" + Environment.TOOLBOX_VERSION + ":dump"),
                List.of("--force-interactive"));

        String log = logs.get("eu.maveniverse.maven.plugins:toolbox:" + Environment.TOOLBOX_VERSION + ":dump");
        assertTrue(log.contains("https://repo1.maven.org/maven2"), log);

    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

 * 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

import org.mockito.Mock;

/**
 * Unit tests for the {@link Info} implementations used by the SMB1
 * protocol handling code.
 */
class InfoTest {

    // A tiny mock to illustrate Mockito interaction patterns.
    @Mock
    private SmbComTransactionResponse transactionMock;

    @BeforeEach
    void setUp() {
        transactionMock = mock(SmbComTransactionResponse.class);
    }

    @Test

        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

{"item_id": 5, "q": "somequery"}
```

## Documentação interativa da API { #interactive-api-docs }

Agora você pode ir para <a href="http://192.168.99.100/docs" class="external-link" target="_blank">http://192.168.99.100/docs</a> ou <a href="http://127.0.0.1/docs" class="external-link" target="_blank">http://127.0.0.1/docs</a> (ou equivalente, usando seu host Docker).

        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

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 }

    void supportsIntegrity_alwaysTrue() {
        assertTrue(ctx.supportsIntegrity());
    }

    @Test
    @DisplayName("calculateMIC returns value from GSS and verifies interaction")
    void calculateMIC_success() throws Exception {
        byte[] data = new byte[] { 1, 2, 3 };
        byte[] mic = new byte[] { 9, 8 };
        when(gssContext.getMIC(eq(data), eq(0), eq(3), any())).thenReturn(mic);