then verify that requests were made as expected.

Because it exercises your full HTTP stack, you can be confident that you're
testing everything. You can even copy & paste HTTP responses from your real web
server to create representative test cases. Or test that your code survives in
awkward-to-reproduce situations like 500 errors or slow-loading responses.


### Example

)
```

/// warning | Advertencia

Las funciones adicionales de soporte `fake_password_hasher` y `fake_save_user` son solo para demostrar un posible flujo de datos, pero por supuesto no proporcionan ninguna seguridad real.

///

## Reducir duplicación

Reducir la duplicación de código es una de las ideas centrales en **FastAPI**.

                }
              }));
    }

    /*
     * 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.

        }
    }

    public void test_scroll_callbackHandling() {
        // This test verifies the scroll method exists and handles callbacks properly
        // Note: In a real test environment, this would require proper SearchEngineClient setup
        // For now, we test that the method signature is correct and can be called

        AtomicInteger callbackCount = new AtomicInteger(0);

                log.warn("Error creating SmbFile from cache for {}: {}", fileInfo.getName(), e.getMessage());
                // For testing purposes, continue processing other files
                // In a real scenario, you might want to handle this differently
            }
        }

        return files;
    }

    /**
     * Update directory cache with new listing
     *

        Smb2CloseRequest request = new Smb2CloseRequest(mockConfig, emptyFileId);

        // When
        request.setFileId(testFileId);

        // Then - verify through internal state (would need getter or reflection in real scenario)
        // Since we can't directly verify the internal state, we create a new request to test
        Smb2CloseRequest newRequest = new Smb2CloseRequest(mockConfig, testFileId);

        // Act
        spyBlob.set(payload);

        // Assert
        verify(spyBlob, times(1)).set(payload);
        assertSame(payload, spyBlob.get(), "Spy should behave like real object exposing same array");
        assertEquals(2, spyBlob.length(), "length() should reflect the set payload length");
    }

    @Test
    void testSend() throws SmbException {
        SmbTree tree = new SmbTree(session, "testShare", "A:");
        tree.connectionState = 2; // Connected state
        tree.tid = 123;

        // Create real request and response objects since they're not interfaces
        ServerMessageBlock request = new SmbComOpenAndX("testfile.txt", 0x01, 0, null);
        ServerMessageBlock response = new SmbComOpenAndXResponse();

a fake `HostnameVerifier` or `X509TrustManager`.

Certificate Authorities
-----------------------

The above example uses a self-signed certificate. This is convenient for testing but not
representative of real-world HTTPS deployment. To get closer to that we can use `HeldCertificate`
to generate a trusted root certificate, an intermediate certificate, and a server certificate.

///

## 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**