# Testing Dependencies with Overrides { #testing-dependencies-with-overrides }

## Overriding dependencies during testing { #overriding-dependencies-during-testing }

There are some scenarios where you might want to override a dependency during testing.

You don't want the original dependency to run (nor any of the sub-dependencies it might have).

# Testing { #testing }

Thanks to <a href="https://www.starlette.io/testclient/" class="external-link" target="_blank">Starlette</a>, testing **FastAPI** applications is easy and enjoyable.

It is based on <a href="https://www.python-httpx.org" class="external-link" target="_blank">HTTPX</a>, which in turn is designed based on Requests, so it's very familiar and intuitive.

    }

    @Test
    void testGetAndSetFlags() {
        // Test setting and getting flags
        int testFlags = 0x12345678;
        message.setFlags(testFlags);
        assertEquals(testFlags, message.getFlags(), "Flags should be set and retrieved correctly.");
    }

    @Test
    void testGetFlag() {
        // Test getting individual flags
        message.setFlags(0b1010); // Set flags: 8 (0x8) and 2 (0x2)

# Testing Events: lifespan and startup - shutdown { #testing-events-lifespan-and-startup-shutdown }

When you need `lifespan` to run in your tests, you can use the `TestClient` with a `with` statement:

{* ../../docs_src/app_testing/tutorial004.py hl[9:15,18,27:28,30:32,41:43] *}


You can read more details about the ["Running lifespan in tests in the official Starlette documentation site."](https://www.starlette.io/lifespan/#running-lifespan-in-tests)

# Testing a Database { #testing-a-database }

You can study about databases, SQL, and SQLModel in the <a href="https://sqlmodel.tiangolo.com/" class="external-link" target="_blank">SQLModel docs</a>. 🤓

There's a mini <a href="https://sqlmodel.tiangolo.com/tutorial/fastapi/" class="external-link" target="_blank">tutorial on using SQLModel with FastAPI</a>. ✨

    public void test_getId_defaultValue() {
        // Test that default ID value is 0
        assertEquals(0L, dictionaryItem.getId());
    }

    public void test_getId_afterSetting() {
        // Test getting ID after setting it
        dictionaryItem.id = 123L;
        assertEquals(123L, dictionaryItem.getId());
    }

    public void test_getId_negativeValue() {
        // Test with negative ID value

# Testing WebSockets { #testing-websockets }

You can use the same `TestClient` to test WebSockets.

For this, you use the `TestClient` in a `with` statement, connecting to the WebSocket:

{* ../../docs_src/app_testing/tutorial002.py hl[27:31] *}

/// note

For more details, check Starlette's documentation for <a href="https://www.starlette.io/testclient/#testing-websocket-sessions" class="external-link" target="_blank">testing WebSockets</a>.

During local development, there is a script that builds the site and checks for any changes, live-reloading:

<div class="termy">

```console
$ python ./scripts/docs.py live

<span style="color: green;">[INFO]</span> Serving on http://127.0.0.1:8008
<span style="color: green;">[INFO]</span> Start watching changes
<span style="color: green;">[INFO]</span> Start detecting changes
```

</div>

Add below section to your `prometheus.yml`
```yaml
alerting:
  alertmanagers:
  - static_configs:
    - targets: ['localhost:9093']
rule_files:
  - rules.yml
```
Here `rules.yml` is the file which should contain the alerting rules defined.

## Add rules for your deployment

        super.tearDown();
    }

    // Test basic property retrieval
    public void test_get_basicProperty() {
        // Test getting a property from the config
        String value = fessConfig.get("domain.title");
        assertEquals("Test Fess", value);

        // Test getting another property
        String engineType = fessConfig.get("search_engine.type");
        assertEquals("opensearch", engineType);
    }