ObjectSizeLessThan: 100 * humanize.MiByte,
	}
	fiLtAndGt := Filter{
		And: And{
			ObjectSizeGreaterThan: 1 * humanize.MiByte,
			ObjectSizeLessThan:    100 * humanize.MiByte,
		},
	}

	tests := []struct {
		filter  Filter
		objSize int64
		want    bool
	}{
		{
			filter:  fiLt,
			objSize: 101 * humanize.MiByte,
			want:    false,
		},
		{
			filter:  fiLt,

///

## Upgrade der FastAPI-Versionen { #upgrading-the-fastapi-versions }

Sie sollten Tests für Ihre App hinzufügen.

Mit **FastAPI** ist das sehr einfach (dank Starlette), schauen Sie sich die Dokumentation an: [Testen](../tutorial/testing.md){.internal-link target=_blank}

- [ ] Provide integration tests (under `<subproject>/src/integTest`) to verify changes from a user perspective.
- [ ] Provide unit tests (under `<subproject>/src/test`) to verify logic.
- [ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes.
- [ ] Ensure that tests pass sanity check: `./gradlew sanityCheck`.
- [ ] Ensure that tests pass locally: `./gradlew <changed-subproject>:quickTest`.

import java.util.Set;
import org.junit.Ignore;

/**
 * Tests for {@code Multiset.elementSet()} not covered by the derived {@code SetTestSuiteBuilder}.
 *
 * @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")

import static org.mockito.Mockito.verify;
import static org.mockito.Mockito.when;

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

import jcifs.SmbConstants;

/**
 * Basic unit tests for {@link SmbConstants}.  The interface only
 * provides {@code static final} constants, so the test suite focuses on
 * value correctness, bit‑mask logic, and some derived properties.
 *

  <modelVersion>4.0.0</modelVersion>

  <groupId>com.squareup.okhttp3</groupId>
  <artifactId>maven-tests</artifactId>
  <version>1.0.0-SNAPSHOT</version>

  <name>maven-tests</name>
  <description>A simple maven-test.</description>

  <properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>

import java.util.Queue;
import org.junit.Ignore;

/**
 * Base class for queue collection tests.
 *
 * @author Jared Levy
 */
@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")

OkHttp HPACK tests
==================

These tests use the [hpack-test-case][1] project to validate OkHttp's HPACK
implementation.  The HPACK test cases are in a separate git submodule, so to
initialize them, you must run:

    git submodule init
    git submodule update

TODO
----

 * Add maven goal to avoid manual call to git submodule init.
 * Make hpack-test-case update itself from git, and run new tests.

    @BeforeEach
    void setUp() {
        MockitoAnnotations.openMocks(this);
        echoResponse = new Smb2EchoResponse(mockConfig);
    }

    @Nested
    @DisplayName("Constructor Tests")
    class ConstructorTests {

        @Test
        @DisplayName("Should create response with configuration")
        void testConstructor() {
            Smb2EchoResponse response = new Smb2EchoResponse(mockConfig);

/**
 * Tester for equals() and hashCode() methods of a class.
 *
 * <p>The simplest use case is:
 *
 * <pre>
 * new EqualsTester().addEqualityGroup(foo).testEquals();
 * </pre>
 *
 * <p>This tests {@code foo.equals(foo)}, {@code foo.equals(null)}, and a few other operations.
 *
 * <p>For more extensive testing, add multiple equality groups. Each group should contain objects