assertFalse(queryMap.containsKey("DOC"));
        assertFalse(queryMap.containsKey("labels.facet_filetype_doc"));
        assertEquals("filetype:others", queryMap.get("labels.facet_filetype_others"));

        // Verify all unique values added to FacetInfo
        List<String> uniqueQueries = new ArrayList<>();
        uniqueQueries.add("filetype:html");
        uniqueQueries.add("field:value");

            }
            this.mechContext.verifyMIC(ml, mechanismListMIC);
        } catch (final CIFSException e) {
            throw new CIFSException("Failed to verify mechanismListMIC", e);
        }
    }

    /**
     * @param mechs
     * @return
     * @throws CIFSException
     */

            // Ensure the transport is connected and ready
            transport.ensureConnected();

            // Verify multi-channel capability (SMB3+ required)
            if (!transport.isSMB2() || !transport.hasCapability(0x00000008)) { // SMB2_GLOBAL_CAP_MULTI_CHANNEL

        // Delete by query
        boolean result = SuggestUtil.deleteByQuery(client, settings, TEST_INDEX, QueryBuilders.termQuery("field", "value1"));
        assertTrue(result);

        // Verify deletion
        client.admin().indices().prepareRefresh(TEST_INDEX).execute().actionGet();
        long count = client.prepareSearch(TEST_INDEX)
                .setQuery(QueryBuilders.termQuery("field", "value1"))

        // When & Then - should handle gracefully
        assertThrows(Exception.class, () -> {
            response.readBytesWireFormat(buffer, offset);
        });
    }

    @Test
    @DisplayName("Should verify NotifyResponse interface implementation")
    void testNotifyResponseInterface() {
        // Then
        assertTrue(response instanceof NotifyResponse);
        assertNotNull(response.getNotifyInformation());

    This applies to `Authorization`, `Cookie`, `Proxy-Authorization`, and `Set-Cookie` headers.
 *  Fix: Don't crash with an `InaccessibleObjectException` when running on JDK17+ with strong
    encapsulation enabled.
 *  Fix: Strictly verify hostnames used with OkHttp's `HostnameVerifier`. Programs that make direct
    manual calls to `HostnameVerifier` could be defeated if the hostnames they pass in are not
    strictly ASCII. This issue is tracked as [CVE-2021-0341].

    --hash=sha256:05c70a234fa14c140aa6d9076135d9550962d95849911b8d5d0419a3add09f00 \
    --hash=sha256:31cbd8045d4ff6776f79bef328b5fd563e5ecc8ae82ea34b6fe5e76efe2a84eb
    # via -r ci/official/requirements_updater/requirements.in
certifi==2025.1.31 \
    --hash=sha256:3d5da6925056f6f18f119200434a4780a94263f10d1c21d032a6f6b2baa20651 \
    --hash=sha256:ca78db4565a652026a4db2bcdf68f2fb589ea80d0be70e03929ed730746b84fe
    # via requests
charset-normalizer==3.4.1 \

    --hash=sha256:05c70a234fa14c140aa6d9076135d9550962d95849911b8d5d0419a3add09f00 \
    --hash=sha256:31cbd8045d4ff6776f79bef328b5fd563e5ecc8ae82ea34b6fe5e76efe2a84eb
    # via -r ci/official/requirements_updater/requirements.in
certifi==2025.1.31 \
    --hash=sha256:3d5da6925056f6f18f119200434a4780a94263f10d1c21d032a6f6b2baa20651 \
    --hash=sha256:ca78db4565a652026a4db2bcdf68f2fb589ea80d0be70e03929ed730746b84fe
    # via requests
charset-normalizer==3.4.1 \

    --hash=sha256:05c70a234fa14c140aa6d9076135d9550962d95849911b8d5d0419a3add09f00 \
    --hash=sha256:31cbd8045d4ff6776f79bef328b5fd563e5ecc8ae82ea34b6fe5e76efe2a84eb
    # via -r ci/official/requirements_updater/requirements.in
certifi==2025.1.31 \
    --hash=sha256:3d5da6925056f6f18f119200434a4780a94263f10d1c21d032a6f6b2baa20651 \
    --hash=sha256:ca78db4565a652026a4db2bcdf68f2fb589ea80d0be70e03929ed730746b84fe
    # via requests
charset-normalizer==3.4.1 \

        String sessionCountId3 = crawlingConfigHelper.store(sessionId, crawlingConfigHelper.getCrawlingConfig("W3"));
        assertEquals("testSession-3", sessionCountId3);

        // Verify stored configs
        assertEquals("1", crawlingConfigHelper.get(sessionCountId1).getId());
        assertEquals("2", crawlingConfigHelper.get(sessionCountId2).getId());