///

## Separando testes

Em uma aplicação real, você provavelmente teria seus testes em um arquivo diferente.

E seu aplicativo **FastAPI** também pode ser composto de vários arquivos/módulos, etc.

### Arquivo do aplicativo **FastAPI**

tener **un programa/servidor HTTP** ejecutándose en el servidor (la máquina, host, etc.) y **gestionando todas las partes de HTTPS**: recibiendo los **requests HTTPS encriptados**, enviando los **requests HTTP desencriptados** a la aplicación HTTP real que se ejecuta en el mismo servidor (la aplicación **FastAPI**, en este caso), tomando el **response HTTP** de la aplicación, **encriptándolo** usando el **certificado HTTPS** adecuado y enviándolo de vuelta al cliente usando **HTTPS**. Este servidor...

        verify(watchHandle, times(1)).call();
    }

    /**
     * Test call() method as Callable in executor service
     */
    @Test
    void testCallAsCallable() throws Exception {
        // Create a real implementation for testing Callable behavior
        SmbWatchHandle realHandle = new SmbWatchHandle() {
            private int callCount = 0;

            @Override

import org.mockito.Mock;
import org.mockito.junit.jupiter.MockitoExtension;

/**
 * JUnit 5 tests for {@link TestLocking}.
 * Tests command line argument parsing and basic field initialization.
 * Does not require a real SMB server - focuses on application logic.
 */
@ExtendWith(MockitoExtension.class)
class TestLockingTest {

    private PrintStream originalOut;
    private PrintStream originalErr;

)
```

/// warning

The supporting additional functions `fake_password_hasher` and `fake_save_user` are just to demo a possible flow of the data, but they of course are not providing any real security.

///

## Reduce duplication { #reduce-duplication }

Reducing code duplication is one of the core ideas in **FastAPI**.

         * This avoids out-of-control memory consumption, and it keeps the cache from growing so
         * large that doing the lookup is noticeably slower than redoing the work would be.
         *
         * Ideally we'd have a real eviction policy, but until we see a problem in practice, I hope
         * that this will suffice. I have not even benchmarked with different size limits.
         */
        if (validClasses.size() > 1000) {

import jcifs.smb.SmbSessionInternal;
import jcifs.smb.SmbTransportInternal;

/**
 * Unit tests for SMB3 Multi-Channel functionality
 *
 * These tests verify the multi-channel implementation without requiring a real SMB server.
 */
@ExtendWith(MockitoExtension.class)
@MockitoSettings(strictness = Strictness.LENIENT)
class MultiChannelIntegrationTest {

    @Mock
    private SmbTransportInternal mockTransport;

    @Mock

            fail("Failed to access servername field: " + e.getMessage());
        }
    }

    @Test
    void testGetEntriesWithMultipleShares() throws Exception {
        // Create real ShareInfo1 objects instead of mocks
        srvsvc.ShareInfo1 shareInfo1 = new srvsvc.ShareInfo1();
        shareInfo1.netname = "Share1";
        shareInfo1.type = 0;
        shareInfo1.remark = "Remark for Share1";

                }
              }));
    }

    /*
     * It's unlikely that any operations would fail by throwing an exception, but let's check them
     * just to be safe.
     *
     * The real purpose of this test is to produce a TSAN failure if MapIteratorCache is unsafe for
     * reads from multiple threads -- unsafe, in fact, even in the absence of a concurrent write.

     */
    @Test
    @DisplayName("Test FileInformation implementation with spy")
    void testFileInformationWithSpy() throws SMBProtocolDecodingException {
        // Create spy on real object
        FileEndOfFileInformation realObject = new FileEndOfFileInformation(4096L);
        FileEndOfFileInformation spy = Mockito.spy(realObject);

        // Call methods