}

    RuntimeException multiples(boolean overflow) {
      if (exceptionSupplier != null) {
        throw exceptionSupplier.get();
      }
      StringBuilder sb =
          new StringBuilder().append("expected one element but was: <").append(element);
      for (Object o : extras) {
        sb.append(", ").append(o);
      }
      if (overflow) {
        sb.append(", ...");
      }
      sb.append('>');

    // The task thread waits for the latch, so we expect a timeout here.
    try {
      future.get(20, MILLISECONDS);
      fail("Should have timed out trying to get the value.");
    } catch (TimeoutException expected) {
    } finally {
      latch.countDown();
    }
  }

  /**
   * Tests that a canceled future throws a cancellation exception.
   *

    },
    "user": {
        "username": "dave",
        "full_name": "Dave Grohl"
    }
}
```

/// note

Notice that even though the `item` was declared the same way as before, it is now expected to be inside of the body with a key `item`.

///

**FastAPI** will do the automatic conversion from the request, so that the parameter `item` receives its specific content and the same for `user`.

// These tests should not be confused with `[*]_grad_test` which compare the
// result of `gradient_checker` and `[*]_grad`. The tests here test the
// functionality of `gradient_checker` by comparing the result with expected
// manual user-provided gradients.
class GradientCheckerTest
    : public ::testing::TestWithParam<std::tuple<const char*, bool, bool>> {
 protected:
  void SetUp() override {
    TF_StatusPtr status(TF_NewStatus());

        SmbResource r = itr.next();

        // Assert: the invalid name was skipped, valid one returned
        assertNotNull(r);
        assertTrue(r.getName().startsWith("OKSERVER"), "Expected valid entry to be adapted");
        assertFalse(itr.hasNext());
    }

    @Test
    @DisplayName("Filter rejects first, accepts second; interactions verified")

 - time-based eviction is applied on top of the cache rather than internally,
   which makes it easier to assert on what the cache is expected to contain at
   a given time.

=== Bad practices

==== Use randomized-testing for coverage

In general, randomization should be used for parameters that are not expected
to affect the behavior of the functionality that is being tested. For instance

1. Export index mappings and settings from source
2. Apply custom analyzers in Fess's `fess_config.properties`
3. Create synonym dictionaries in Fess's dictionary directory

---

### Apache Solr

For migrating from Apache Solr:

#### Document Export and Import

**Step 1: Export from Solr**

```bash
# Export Solr documents as JSON

        indexUpdater.finishCrawling = true;
        indexUpdater.destroy();
        // finishCrawling should be set when max empty list count is exceeded
        // In test environment this may not work as expected
        // assertTrue(indexUpdater.finishCrawling);
    }

    // Test addFinishedSessionId
    @Test
    public void test_addFinishedSessionId() {
        final String sessionId = "session123";

        try {
            testScriptEngine.register();
            fail("Should throw exception when factory is null");
        } catch (NullPointerException e) {
            // Expected exception
        }
    }

    // Test concrete implementation with different name
    @Test
    public void test_differentNameImplementation() {

        assertEquals(option1.getFieldNaming(), option2.getFieldNaming());
    }

    @Test
    public void test_allMethodsReturnExpectedValues() {
        // Comprehensive test to verify all methods return expected values
        FessJsonResourceProvider testProvider = new FessJsonResourceProvider();

        // Verify nulls suppression is enabled
        assertTrue("Nulls should be suppressed", testProvider.isNullsSuppressed());