import org.junit.Ignore;

/**
 * Superclass for all {@code Multimap} testers.
 *
 * @author Louis Wasserman
 */
@GwtCompatible
@Ignore("test runners must not instantiate and run this directly, only via suites we build")
// @Ignore affects the Android test runner, which respects JUnit 4 annotations on JUnit 3 tests.
@SuppressWarnings("JUnit4ClassUsedInJUnit3")
@NullMarked

import java.util.Iterator;
import java.util.List;
import org.junit.Ignore;

/**
 * Common superclass for {@link MultisetSetCountUnconditionallyTester} and {@link
 * MultisetSetCountConditionallyTester}. It is used by those testers to test calls to the
 * unconditional {@code setCount()} method and calls to the conditional {@code setCount()} method
 * when the expected present count is correct.
 *
 * @author Chris Povirk
 */
@GwtCompatible

/// tip | Tipp

Wenn Sie in Ihren Tests neben dem Senden von <abbr title="Request – Anfrage: Daten, die der Client zum Server sendet">Requests</abbr> an Ihre FastAPI-Anwendung auch `async`-Funktionen aufrufen möchten (z. B. asynchrone Datenbankfunktionen), werfen Sie einen Blick auf die [Async-Tests](../advanced/async-tests.md) im Handbuch für fortgeschrittene Benutzer.

///

## Tests separieren { #separating-tests }

---
- job:
    name: elastic+elasticsearch+%BRANCH%+multijob+third-party-tests-azure-sas
    workspace: /dev/shm/elastic+elasticsearch+%BRANCH%+multijob+third-party-tests-azure-sas
    display-name: "elastic / elasticsearch # %BRANCH% - third party tests azure - sas token"
    description: "Testing of the Elasticsearch %BRANCH% third party tests against Azure using SAS token\n"
    builders:
      - inject:
          properties-file: '.ci/java-versions.properties'

---
- job:
    name: "elastic+elasticsearch+pull-request+packaging-tests-windows-sample"
    display-name: "elastic / elasticsearch - pull request packaging-tests-windows-sample"
    description: "Testing of Elasticsearch pull requests - packaging-tests-windows-sample"
    # We use a hard-coded workspace directory here to avoid hitting windows path length limits
    child-workspace: "C:\\Users\\jenkins\\workspace\\pr-packaging-windows\\${BUILD_NUMBER}"

///

### Support des éditeurs { #editor-support }

Tout le framework a été conçu pour être facile et intuitif à utiliser, toutes les décisions ont été testées sur plusieurs éditeurs avant même de commencer le développement, pour assurer la meilleure expérience de développement.

    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <!--
    Some tests need reflective access to the internals of these packages. It is only the
    tests themselves and not the code being tested that needs that access, though there's no
    obvious way to ensure that.

    We could consider arranging things so that only the tests we know need this would get
    the add-opens. Right now that doesn't seem worth the effort, though.

    if (!e.getMessage().contains(message)) {
      fail("expected <" + e.getMessage() + "> to contain <" + message + ">");
    }
  }

  /**
   * Test class with valid equals and hashCode methods. Testers created with instances of this class
   * should always pass.
   */
  private static class ValidTestObject {
    private final int aspect1;
    private final int aspect2;

* Sie können `.env`-Dateien damit verwenden.

---
- job:
    name: "elastic+elasticsearch+pull-request+packaging-tests-windows-sample-nojdk"
    display-name: "elastic / elasticsearch - pull request packaging-tests-windows-sample-nojdk"
    description: "Testing of Elasticsearch pull requests - packaging-tests-windows-sample-nojdk"
    # We use a hard-coded workspace directory here to avoid hitting windows path length limits
    child-workspace: "C:\\Users\\jenkins\\workspace\\pr-packaging-windows\\${BUILD_NUMBER}"