# Testando Dependências com Sobreposição (Overrides)

## Sobrepondo dependências durante os testes

Existem alguns cenários onde você deseje sobrepor uma dependência durante os testes.

Você não quer que a dependência original execute (e nenhuma das subdependências que você possa ter).

Nesse cenário, se você precisa manipular essa exceção de modo global com o FastAPI, você pode adicionar um manipulador de exceção customizada com `@app.exception_handler()`.

{* ../../docs_src/handling_errors/tutorial003.py hl[5:7,13:18,24] *}

    }

    /**
     * Test watch() method returning empty list when buffer overflow
     */
    @Test
    void testWatchBufferOverflow() throws CIFSException {
        // Setup mock behavior for buffer overflow scenario
        when(watchHandle.watch()).thenReturn(Collections.emptyList());

        // Execute
        List<FileNotifyInformation> result = watchHandle.watch();

        // Verify
        assertNotNull(result);

ALIAS_NAME=myminio
BUCKET="test-bucket"
DEST_DIR="/tmp/dest"

OUT=$(./mc cp --quiet --recursive "${ALIAS_NAME}"/"${BUCKET}"/initial-data/ "${DEST_DIR}"/)
RET=${?}
if [ ${RET} -ne 0 ]; then
	# It is a success scenario as get objects should fail
	echo "GET objects failed as expected"
	echo "script passed" >resiliency-verify-failure.log
	exit 0
else
	echo "GET objects expected to fail, but succeeded: ${OUT}"

- An inefficient lock in EndpointSlice controller metrics cache has been reworked. Network programming latency may be significantly reduced in certain scenarios, especially in clusters with a large number of Services. ([#107091](https://github.com/kubernetes/kubernetes/pull/107091), [@robscott](https://github.com/robscott))

In an advanced scenario where you know you need the dependency to be called at every step (possibly multiple times) in the same request instead of using the "cached" value, you can set the parameter `use_cache=False` when using `Depends`:

/// note | Nota

`jsonable_encoder` es utilizado internamente por **FastAPI** para convertir datos. Pero es útil en muchos otros escenarios.

    void testCapacityEdgeValues(long capacity) {
        when(mockAllocInfo.getCapacity()).thenReturn(capacity);
        assertEquals(capacity, mockAllocInfo.getCapacity());
    }

    /**
     * Null pointer scenario – calls on a null reference should raise
     * {@link NullPointerException}. This test is defensive; in real code it
     * would likely be handled elsewhere.
     */
    @Test

    }

    public void test_exceptionInComplexScenario() {
        // Test exception in a more complex scenario
        InvalidAccessTokenException exception = null;
        String expectedType = "Bearer";
        String expectedMessage = "Token has expired";

        // Simulate a token validation scenario
        boolean tokenValid = false;
        if (!tokenValid) {

    @Test
    @DisplayName("send with explicit null varargs propagates exception from implementation")
    void send_nullVarargsArray_throws() throws Exception {
        // Arrange: passing explicit null vararg array is edge scenario
        when(tree.send(eq(request), isNull())).thenThrow(new CIFSException("null params"));

        // Act + Assert