{* ../../docs_src/dependencies/tutorial005_an_py310.py hl[8:9] *}

It declares an optional query parameter `q` as a `str`, and then it just returns it.

This is quite simple (not very useful), but will help us focus on how the sub-dependencies work.

## Second dependency, "dependable" and "dependant" { #second-dependency-dependable-and-dependant }

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

/**
 * Tests for the {@link AllocInfo} interface.
 * Since {@code AllocInfo} only declares getters, the tests focus on
 * verifying that implementations honour the contract.
 */
@ExtendWith(MockitoExtension.class)
public class AllocInfoTest {

    @Mock
    AllocInfo mockAllocInfo;

    /**

## First Steps { #first-steps }

Let's see a very simple example. It will be so simple that it is not very useful, for now.

But this way we can focus on how the **Dependency Injection** system works.

### Create a dependency, or "dependable" { #create-a-dependency-or-dependable }

Let's first focus on the dependency.

It is just a function that can take all the same parameters that a *path operation function* can take:

    void close_doesNothing() throws Exception {
        // Arrange
        SmbPipeOutputStream out = newStream();
        // constructor already calls handle.getPipe(); clear interactions to focus on close()
        clearInvocations(handle);

        // Act
        out.close();

        // Assert
        verifyNoInteractions(handle);
    }

    @Nested

import org.junit.jupiter.api.Nested;
import org.junit.jupiter.api.Test;
import org.mockito.Mockito;

/**
 * Tests for {@link WinError} interface constants and static arrays.
 * The interface has no instance methods, so the tests focus on
 * value correctness and array integrity.  A tiny Mockito example
 * demonstrates that the interface can be mocked if another class
 * depends on it.
 */
public class WinErrorTest {

    @Nested

        // For 100% coverage, we'd need to ensure the superclass constructor is indeed called with these values.
        // However, given the current structure, testing the fields set by MsrpcEnumerateAliasesInDomain itself is the primary focus.
    }

import org.junit.jupiter.api.DisplayName;
import org.junit.jupiter.api.Nested;
import org.junit.jupiter.api.Test;

/**
 * Unit tests for {@link SmbFileFilter}. The filter interface is small; the
 * tests focus on the contract that implementations should honour and the
 * interaction with {@link SmbFile} instances. The tests make heavy use of
 * Mockito to guarantee that implementation classes do not inadvertently
 * bypass the filter logic.

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

import jcifs.Configuration;

/**
 * Tests for {@link SmbComSetInformationResponse}.
 *
 * Tests focus on the wire format methods which all return 0,
 * and the toString method implementation.
 */
@ExtendWith(MockitoExtension.class)
@DisplayName("SmbComSetInformationResponse tests")

        }
    }

    // Note: This test is simplified because complex Tomcat Context mocking
    // is difficult to maintain due to frequent API changes.
    // The focus is on testing the class structure and basic functionality
    // that can be verified without full integration testing.

/**
 * Unit tests for {@link TransWaitNamedPipeResponse}.
 *
 * The implementation contains only trivial methods that return {@code 0}
 * or construct a string representation.  The tests focus on:
 *
 * <ul>
 *   <li>happy‑path behaviour</li>
 *   <li>boundary arguments (e.g., negative indices, large values)</li>
 *   <li>string representation containing the class name</li>
 *   <li>null buffer handling</li>