* supported. Null keys and values are supported.
 *
 * <p>{@code containsKey(k)}, {@code put(k, v)} and {@code remove(k)} are all (expected and
 * amortized) constant time operations. Expected in the hashtable sense (depends on the hash
 * function doing a good job of distributing the elements to the buckets to a distribution not far

      for (expectedClass in allowedExceptionTypes) {
        if (expectedClass.isInstance(failure)) {
          found = true
          break
        }
      }
      assertThat(
        found,
        "Expected exception type among ${allowedExceptionTypes.contentToString()}, got $failure",
      ).isTrue()
    }

  fun assertFailure(vararg messages: String) =
    apply {

        try {
            queryCommand.execute(queryContext, termQuery, 1.0f);
            fail("Should throw InvalidQueryException");
        } catch (InvalidQueryException e) {
            // Expected exception
            assertTrue(e.getMessage().contains("Unknown q:"));
        }
    }

    public void test_toLowercaseWildcard_enabled() {
        queryCommand.setLowercaseWildcard(true);

   * than a one-character array containing the character itself. This enables the escaping algorithm
   * to perform more efficiently.
   *
   * <p>An escaper is expected to be able to deal with any {@code char} value, so this method should
   * not throw any exceptions.
   *
   * @param c the character to escape if necessary

        PropertyConfiguration emptyConfig = new PropertyConfiguration(emptyProps);

        // Then
        assertNotNull(emptyConfig);
        // Hostname may be null when not provided in properties
        // This is expected behavior
    }

    @Test
    @DisplayName("Should parse integer properties correctly")
    void testIntegerProperties() throws CIFSException {
        // Given
        Properties props = new Properties();

                        session.acquire();
                        acquireCount.incrementAndGet();
                    }

                } catch (Exception e) {
                    // Ignore expected exceptions from over-release
                } finally {
                    endLatch.countDown();
                }
            });
        }

        // Start all threads simultaneously

success=$(./mc admin heal -r sitea/bucket/README.md --json --force | jq -r 'select((.name == "bucket/README.md") and (.after.color == "green")) | .after.color == "green"')
if [ "${success}" != "true" ]; then
	echo "Found bug expected transitioned object to report 'green'"
	exit 1
fi

The same way as with regular header parameters, when you have underscore characters in the parameter names, they are **automatically converted to hyphens**.

For example, if you have a header parameter `save_data` in the code, the expected HTTP header will be `save-data`, and it will show up like that in the docs.

If for some reason you need to disable this automatic conversion, you can do it as well for Pydantic models for header parameters.

            // Should catch the exception and return EXIT_FAIL
            assertEquals(Constants.EXIT_FAIL, result);
        } catch (RuntimeException e) {
            // Expected behavior - test exception propagates
            assertEquals("Test exception", e.getMessage());
        }
    }

    // Test writeTimeToSessionInfo method

    char[] sharedArray = new char[arraysDim2];
    Arrays.fill(arrays, sharedArray);

    try {
      Chars.concat(arrays);
      fail();
    } catch (IllegalArgumentException expected) {
    }
  }

  @GwtIncompatible // Chars.fromByteArray
  public void testFromByteArray() {
    assertThat(Chars.fromByteArray(new byte[] {0x23, 0x45, (byte) 0xDC})).isEqualTo('\u2345');