}

    public void test_addCondition() {
        // Test adding conditions
        generator = new TestThumbnailGenerator();

        // Test adding single condition
        generator.addCondition("field1", "value1");

        // Test adding multiple conditions for same field
        generator.addCondition("field1", "value2");

        // Test adding conditions for different fields

@SuppressWarnings("JUnit4ClassUsedInJUnit3")
public abstract class AbstractMultisetSetCountTester<E> extends AbstractMultisetTester<E> {
  /*
   * TODO: consider adding MultisetFeatures.SUPPORTS_SET_COUNT. Currently we
   * assume that using setCount() to increase the count is permitted iff add()
   * is permitted and similarly for decrease/remove(). We assume that a

        assertTrue(result.isPartialResults());
        assertNull(result.getFacetResponse());
    }

    public void test_builder_withDocuments() {
        // Test builder with adding documents
        Map<String, Object> doc1 = new HashMap<>();
        doc1.put("id", "1");
        doc1.put("title", "Document 1");

        Map<String, Object> doc2 = new HashMap<>();
        doc2.put("id", "2");

        // Test with empty strings
        result = jobExecutor.execute("", "");
        assertEquals("Executed:  ", result);
    }

    public void test_addShutdownListener() {
        // Test adding shutdown listener
        AtomicBoolean shutdownCalled = new AtomicBoolean(false);
        ShutdownListener listener = new ShutdownListener() {
            @Override
            public void onShutdown() {

@SuppressWarnings("JUnit4ClassUsedInJUnit3")
public abstract class AbstractMultisetSetCountTester<E> extends AbstractMultisetTester<E> {
  /*
   * TODO: consider adding MultisetFeatures.SUPPORTS_SET_COUNT. Currently we
   * assume that using setCount() to increase the count is permitted iff add()
   * is permitted and similarly for decrease/remove(). We assume that a

        assertEquals("newName", emptyGenerator.getName());
    }

    public void test_addCondition() {
        // Initialize without container
        emptyGenerator = new EmptyGenerator();

        // Test adding conditions - this should work without container
        emptyGenerator.addCondition("field1", "pattern1");
        emptyGenerator.addCondition("field1", "pattern2");
        emptyGenerator.addCondition("field2", "pattern.*");

 * {@code asMap} has a few subtleties. As long as the set of keys remains unchanged, adding or
 * removing mappings does not affect the key iteration order. However, if you remove all values
 * associated with a key and then add the key back to the multimap, that key will come last in the
 * key iteration order.
 *
 * <p>The multimap does not store duplicate key-value pairs. Adding a new key-value pair equal to an
 * existing key-value pair has no effect.
 *

 *
 * @author Chris Povirk
 */
/*
 * The whole thing is really @GwtIncompatible, but GwtJUnitConvertedTestModule doesn't have a
 * parameter for non-GWT, non-test files, and it didn't seem worth adding one for this unusual case.
 */
@GwtCompatible
@NullUnmarked
final class LenientSerializableTester {
  /*
   * TODO(cpovirk): move this to c.g.c.testing if we allow for c.g.c.annotations dependencies so

 *
 * <p>When iterating through the collections supplied by this class, the ordering of values for a
 * given key agrees with the order in which the values were added.
 *
 * <p>This multimap allows duplicate key-value pairs. After adding a new key-value pair equal to an
 * existing key-value pair, the {@code ArrayListMultimap} will contain entries for both the new
 * value and the old value.
 *

  // safely publish these objects and we won't need this whole discussion.
  // TODO(user,lukes): consider adding volatile to all these fields since in current known JVMs
  // that should resolve the issue. This comes at the cost of adding more write barriers to the
  // implementations.

  private Futures() {}

  /**