To send data, you should use one of: `POST` (the more common), `PUT`, `DELETE` or `PATCH`.

Sending a body with a `GET` request has an undefined behavior in the specifications, nevertheless, it is supported by FastAPI, only for very complex/extreme use cases.

As it is discouraged, the interactive docs with Swagger UI won't show the documentation for the body when using `GET`, and proxies in the middle might not support it.

///

    assertFalse(set.equals(newHashSet(4, 5, 6)));
    assertFalse(newHashSet(4, 5, 6).equals(set));

    Set<String> complex = Sets.newTreeSet(STRING_LENGTH);
    Collections.addAll(complex, "in", "the", "a");
    assertEquals(set, complex);
  }

  public void testEquals_bothDefaultOrdering_stringVsInt() {
    SortedSet<String> set = of("a", "b", "c");

        RankFusionSearcher simpleSearcher = new SimpleSearcher();
        assertEquals("simple", simpleSearcher.getName());
    }

    public void test_getName_complexCamelCaseSearcher() {
        // Test with complex camel case naming
        RankFusionSearcher complexSearcher = new VeryComplexRankFusionSearcher();
        assertEquals("very_complex_rank_fusion", complexSearcher.getName());
    }

        }

        @Test
        @DisplayName("Should decode array correctly")
        void testDecode() throws NdrException {
            // Given: Mocked buffer data with pre-created entries to avoid complex entry decode chain
            samr.SamrSamArray array = new samr.SamrSamArray();
            array.entries = new samr.SamrSamEntry[1]; // Pre-populate to avoid decoding
            array.entries[0] = new samr.SamrSamEntry();

        assertNotSame(unknownException.getMessageCode(), parseException.getMessageCode());
    }

    public void test_complexMessageCode() {
        // Setup - test with a complex message code that includes parameters
        final String queryString = "field:value AND (";
        final VaMessenger<FessMessages> complexMessageCode =

 * Due to the iterator's constructor calling advance() immediately, which requires
 * the adapt() method to be functional, we test the behavior using simple mock
 * scenarios that don't require complex filter setups.
 */
@ExtendWith(MockitoExtension.class)
class DirFileEntryAdapterIteratorTest {

    @Mock
    private SmbResource mockParent;

    @Mock
    private CloseableIterator<FileEntry> mockDelegate;

        assertNull(testDfs.getTrustedDomains(auth));
    }

    @Test
    void testGetTrustedDomains_Success() throws IOException, SmbAuthException {
        // This test is complex due to static method dependencies and reflection access
        // For now, we'll test the disabled path which is safer
        testDfs.setDisabled(true);
        assertNull(testDfs.getTrustedDomains(auth));
    }

        assertTrue(result instanceof BoolQueryBuilder);

        BoolQueryBuilder boolResult = (BoolQueryBuilder) result;
        assertEquals(5, boolResult.should().size());
    }

    // Test complex query with all clause types
    public void test_convertBooleanQuery_complexQuery() {
        BooleanQuery.Builder boolQueryBuilder = new BooleanQuery.Builder();

        // Add multiple clauses of each type

 *
 * <p><dfn>Dependency collection</dfn> builds a graph of {@link org.apache.maven.api.Node} objects containing
 * all the dependencies.</p>
 *
 * <p>The <dfn>Dependency graph flattening</dfn> process in Maven reduces a complex,
 * multi-level dependency graph to a map of ordered lists that can be turned into classpaths.
 * During this process only the most relevant version of each artifact

        // Assert
        assertEquals("Status of test-cluster is changed to RED.", result);
        // Note: Notification sending is tested but we don't verify the mock since it uses complex callback mechanism
    }

    // Test state change with empty notification addresses
    public void test_execute_stateChangeEmptyNotificationAddresses() {
        // Setup mock components