Das ist der Vorteil von Standards ...

///

## Es in Aktion sehen

Öffnen Sie die interaktive Dokumentation: <a href="http://127.0.0.1:8000/docs" class="external-link" target="_blank">http://127.0.0.1:8000/docs</a>.

### Authentifizieren

Klicken Sie auf den Button „Authorize“.

Ese es el beneficio de los estándares...

///

## Verlo en acción

Abre la documentación interactiva: <a href="http://127.0.0.1:8000/docs" class="external-link" target="_blank">http://127.0.0.1:8000/docs</a>.

### Autenticar

Haz clic en el botón "Authorize".

Usa las credenciales:

Usuario: `johndoe`

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 }

            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/";

   * may be sent after response headers or body bytes have been received.
   *
   * Though any call may be initiated as a duplex call, only web servers that are specially
   * designed for this nonstandard interaction will use it. As of 2019-01, the only widely-used
   * implementation of this pattern is [gRPC][grpc].
   *
   * Because the encoding of interleaved data is not well-defined for HTTP/1, duplex request

        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(3.14, captured.get("double"));
        assertNotNull(captured.get("map"));
    }

    public void test_store_withCallbackInteraction() {
        // Test store with callback interaction
        final TestIndexUpdateCallback callback = new TestIndexUpdateCallback();

        dataStore = new DataStore() {
            @Override

        // Avoid real JAAS by stubbing getSubject
        doReturn(new Subject()).when(auth).getSubject();

        // Act
        CredentialsInternal result = auth.renew();

        // Assert interaction and return value
        assertSame(auth, result);
        verify(auth, times(1)).getSubject();
    }

/// warning | Aviso

Uma `Response` retornada diretamente em sua *função de operação de rota* não será documentada no OpenAPI (por exemplo, o `Content-Type` não será documentado) e não será visível na documentação interativa automática.

///

/// info | Informação

Obviamente, o cabeçalho `Content-Type`, o código de status, etc, virão do objeto `Response` que você retornou.

///