// Create new file
    testFile.createNewFile();
    
    // Wait for change notification
    Thread.sleep(2000);
    
    // Cache should be invalidated, new listing should include new file
    SmbFile[] updatedFiles = dir.listFiles();
    assertEquals(initialFiles.length + 1, updatedFiles.length);
}
```

## 9. Error Handling

### 9.1 Cache Consistency
```java

            // When
            String name = mockResource.getName();

            // Then
            assertEquals(expectedName, name, "Directory name should include trailing slash");
            assertTrue(name.endsWith("/"), "Directory name should end with slash");
        }
    }

    @Nested
    @DisplayName("Resource Type Tests")
    class ResourceTypeTests {

   * @throws IllegalArgumentException if {@code node} is not an element of this graph
   */
  @Override
  Set<N> successors(N node);

  /**
   * Returns a live view of the edges in this graph whose endpoints include {@code node}.
   *
   * <p>This is equal to the union of incoming and outgoing edges.
   *
   * <p>If {@code node} is removed from the graph after this method is called, the {@code Set}

    message = "moved to val",
    replaceWith = ReplaceWith(expression = "secure"),
    level = DeprecationLevel.ERROR,
  )
  fun secure(): Boolean = secure

  /**
   * @param forObsoleteRfc2965 true to include a leading `.` on the domain pattern. This is
   *     necessary for `example.com` to match `www.example.com` under RFC 2965. This extra dot is
   *     ignored by more recent specifications.
   */

///

### `response_model_include` et `response_model_exclude` { #response-model-include-and-response-model-exclude }

Vous pouvez également utiliser les paramètres du *décorateur de chemin d'accès* `response_model_include` et `response_model_exclude`.

Ils prennent un `set` de `str` avec les noms des attributs à inclure (en omettant le reste) ou à exclure (en incluant le reste).

<dt>`compileOnly`</dt><dd>Code that is on the classpath at compile time but that
should not be shipped with the project because it is "provided" by the runtime
somehow. Elasticsearch plugins use this configuration to include dependencies
that are bundled with Elasticsearch's server.</dd>
<dt>`testImplementation`</dt><dd>Code that is on the classpath for compiling tests
that are part of this project but not production code. The canonical example

YAML REST tests that include x-pack specific APIs need to explicitly declare
which APIs are required through a similar `includeXpack` configuration.

The REST tests are run automatically when executing the "./gradlew check" command. To run only the
YAML REST tests use the following command (modules and plugins may also include YAML REST tests):

            setupListCondition(cb, crawlingInfoPager);
        });

        // update pager
        BeanUtil.copyBeanToBean(crawlingInfoList, crawlingInfoPager, option -> option.include(Constants.PAGER_CONVERSION_RULE));
        crawlingInfoPager.setPageNumberList(
                crawlingInfoList.pageRange(op -> op.rangeSize(fessConfig.getPagingPageRangeSizeAsInteger())).createPageNumberList());

        }).useForm(SearchForm.class, setup -> {
            setup.setup(form -> {
                copyBeanToBean(synonymPager, form, op -> op.include("id"));
            });
        });
    }

    private HtmlResponse asEditHtml() {
        return asHtml(path_AdminDictSynonym_AdminDictSynonymEditJsp);
    }

     * of calculating the complete dependency tree in terms of artifact coordinates. In contrast to dependency
     * resolution, this does not include the download of the files for the dependency artifacts. It is meant for mojos
     * that only want to analyze the set of transitive dependencies, in particular during early lifecycle phases where