* <a href="https://github.com/swagger-api/swagger-ui" class="external-link" target="_blank"><strong>Swagger UI</strong></a>، با <abbr title="interactive exploration">کاوش تعاملی</abbr>، API خود را مستقیما از طریق مرورگر صدازده و تست کنید.

![Swagger UI interaction](https://fastapi.tiangolo.com/img/index/index-03-swagger-02.png)

/**
 * Provides the API for the Maven Shell tool ({@code mvnsh}).
 *
 * <p>This package contains interfaces and classes for the interactive Maven shell,
 * which provides a command-line interface for executing Maven commands and
 * managing build environments.</p>
 *
 * <p>Key features include:</p>
 * <ul>
 *   <li>Interactive command-line interface</li>
 *   <li>Command history and completion</li>
 *   <li>Built-in shell commands</li>

**Community Impact**: A serious violation of community standards, including
sustained inappropriate behavior.

**Consequence**: A temporary ban from any interaction or public
communication with the community for a specified period. No public or
private interaction with the people involved, including unsolicited interaction
with those enforcing the Code of Conduct, is allowed during this period.
Violating these terms may lead to a permanent ban.

     * verifying interaction.
     */
    private class RecordingFilter implements SmbFileFilter {
        private SmbFile lastFile;
        private String lastPath;

        @Override
        public boolean accept(SmbFile file) throws SmbException {
            lastFile = file;
            // Actually interact with the file to verify the mock interaction
            if (file != null) {

**FastAPI** is based on **OpenAPI**.

That's what makes it possible to have multiple automatic interactive documentation interfaces, code generation, etc.

OpenAPI has a way to define multiple security "schemes".

By using them, you can take advantage of all these standard-based tools, including these interactive documentation systems.

OpenAPI defines the following security schemes:

        // Act: invoke renew()
        CredentialsInternal result = renewable.renew();

        // Assert: verify interaction and returned value
        verify(renewable, times(1)).renew();
        assertSame(returned, result, "renew() should return the stubbed value");

        // Negative interaction check: no further interactions with the mock
        verifyNoMoreInteractions(renewable);
    }

    @Test

{* ../../docs_src/path_operation_configuration/tutorial004_py310.py hl[17:25] *}

It will be used in the interactive docs:

<img src="/img/tutorial/path-operation-configuration/image02.png">

## Response description { #response-description }

You can specify the response description with the parameter `response_description`:

import jcifs.internal.Request;

/**
 * Tests for SmbTreeInternal interface behavior via mocks.
 * Since this is an interface, we validate its public API contract
 * through interaction testing and generic type usage.
 */
@ExtendWith(MockitoExtension.class)
class SmbTreeInternalTest {

    @Mock
    private SmbTreeInternal tree;

    @Mock
    private CIFSContext context;

    @Mock

```console
$ fastapi dev main.py

<span style="color: green;">INFO</span>:     Uvicorn running on http://127.0.0.1:8000 (Press CTRL+C to quit)
```

</div>

## Check it { #check-it }

Go to the interactive docs at: <a href="http://127.0.0.1:8000/docs" class="external-link" target="_blank">http://127.0.0.1:8000/docs</a>.

You will see something like this:

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

    }

    // Simple collaborator to demonstrate interaction verification with Mockito
    interface Handler {
        void handle(int code, String message);
    }

    @Mock
    Handler handler;

    @Test
    @DisplayName("Interaction: handler called with each code/message pair")
    void interaction_with_mock_handler_is_as_expected() {
        // Interaction test: simulate passing each code/message to a collaborator