enable-cache: true
          cache-dependency-glob: |
            requirements**.txt
            pyproject.toml
      - name: Install Dependencies
        run: uv pip install -r requirements-tests.txt
      - run: mkdir coverage
      - name: Test
        if: matrix.codspeed != 'codspeed'
        run: bash scripts/test.sh
        env:

import com.google.common.collect.testing.google.ListGenerators.ImmutableListTailSubListGenerator;
import com.google.common.collect.testing.google.ListGenerators.UnhashableElementsImmutableListGenerator;
import com.google.common.collect.testing.testers.ListHashCodeTester;
import com.google.common.testing.CollectorTester;
import com.google.common.testing.NullPointerTester;
import com.google.common.testing.SerializableTester;
import java.util.Arrays;

    @Test
    void testDfsImplConstructor() {
        // The constructor is called in setUp(), so if no exception is thrown, this test passes.
        assertNotNull(dfsImpl);
    }

    // Tests for isTrustedDomain
    @Test
    void testIsTrustedDomain_DfsDisabled() throws SmbAuthException {
        // Scenario: DFS is disabled in the configuration.
        when(mockConfig.isDfsDisabled()).thenReturn(true);

**FastAPI** は開発者の利便性のために `fastapi.testclient` と同じ `starlette.testclient` を提供します。しかし、実際にはStarletteから直接渡されています。

///

/// tip | 豆知識

FastAPIアプリケーションへのリクエストの送信とは別に、テストで `async` 関数 (非同期データベース関数など) を呼び出したい場合は、高度なチュートリアルの[Async Tests](../advanced/async-tests.md){.internal-link target=_blank} を参照してください。

///

## テストの分離

実際のアプリケーションでは、おそらくテストを別のファイルに保存します。

また、**FastAPI** アプリケーションは、複数のファイル/モジュールなどで構成されている場合もあります。

### **FastAPI** アプリファイル

package jcifs.smb1.smb1;

/**
 * Unit tests for {@link FileEntry}. The interface itself has no
 * implementation, so the tests exercise the contract via Mockito mocks.
 * Each method is exercised for normal inputs, extreme or edge cases, and
 * interaction verification.
 */
import static org.junit.jupiter.api.Assertions.assertEquals;
import static org.junit.jupiter.api.Assertions.assertNull;
import static org.mockito.Mockito.mock;

import org.jspecify.annotations.NullUnmarked;
import org.junit.Test;
import org.junit.runner.RunWith;
import org.junit.runners.JUnit4;

/** Tests for ordering the elements of graphs. */
@RunWith(JUnit4.class)
@NullUnmarked
public final class ElementOrderTest {
  // Node order tests

  @Test
  public void nodeOrder_none() {
    MutableGraph<Integer> graph = GraphBuilder.directed().nodeOrder(unordered()).build();

mvn license:format

# Run static analysis
mvn spotbugs:check
```

### Running Tests

```bash
# Run all tests
mvn test

# Run specific test class
mvn test -Dtest=CrawlerTest

# Run specific test method
mvn test -Dtest=CrawlerTest#test_execute_web

# Run tests for specific module
mvn test -pl fess-crawler
```

## Examples

### Web Crawling with Custom Rules

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

@DisplayName("DcerpcConstants Tests")
class DcerpcConstantsTest {

    @Nested
    @DisplayName("UUID Constants Tests")
    class UuidConstantsTests {

        @Test
        @DisplayName("DCERPC_UUID_SYNTAX_NDR should have correct UUID value")
        void testDcerpcUuidSyntaxNdr() {

  if (project.name == "regression-test") return@subprojects
  if (project.name == "android-test-app") return@subprojects
  if (project.name == "container-tests") return@subprojects
  if (project.name == "module-tests") return@subprojects

  apply(plugin = "checkstyle")
  apply(plugin = "ru.vyarus.animalsniffer")

  // The 'java' plugin has been applied, but it is not compatible with the Android plugins.

aspects of a component while ignoring others.

These stubs form an internally consistent data-set that is not expected to change. They are
used to test the individual components in the lifecycle with data that has expected characteristics
and can be asserted as desired.

You can change/extend these stubs, and tests should not be breaking too much, since most tests