findNtStatus(dosErr).ifPresent(mock::consume);
        verify(mock).consume(expectedNt);
    }

    @Test
    @DisplayName("DOS_ERROR_MESSAGES length matches expectations")
    void testMessageArrayLength() {
        assertNotNull(DosError.DOS_ERROR_MESSAGES, "DOS_ERROR_MESSAGES should be non‑null");

thousands of people who have already contributed to our projects — and we want to ensure our community
continues to be truly open for everyone.

This code of conduct outlines our expectations for participants, as well as steps to reporting
unacceptable behavior. We are committed to providing a welcoming and inspiring community for all and
expect our code of conduct to be honored.

public class SmbResourceLocatorTest {

    /**
     * A very small concrete implementation used only by the tests. It parses
     * the URL string and performs minimal validation – just enough to make the
     * happy-path expectations deterministic.
     */
    private static class DummySmbResourceLocator implements SmbResourceLocator {
        private final String urlStr;
        private final String host;
        private final String path;

```

### Rewriting Responses

Symmetrically, interceptors can rewrite response headers and transform the response body. This is generally more dangerous than rewriting request headers because it may violate the webserver's expectations!

Since the name of the property is the primary source of immediate information for users, both the names themselves and their structure should convey enough information to set the right expectations.

Previously, there was no formalization of property naming; only loose conventions were followed.

    assertThat(matcher.trimFrom(s)).isEqualTo("");
    assertEquals(s.length(), matcher.countIn(s));
  }

  // Kotlin subSequence()/replace() always return new strings, violating expectations of this test
  @J2ktIncompatible
  public void testGeneral() {
    doTestGeneral(is('a'), 'a', 'b');
    doTestGeneral(isNot('a'), 'b', 'a');
    doTestGeneral(anyOf("x"), 'x', 'z');

      to the package docs.
   9. Test methods are a good place to add Javadoc, because you can use it
      to succinctly describe e.g. preconditions, actions and expectations
      of the test, more easily that just using the test name alone. Please
      consider documenting your tests in this way.
   10. Sometimes you shouldn't add Javadoc:

- Clarified the CFS quota as 100ms in the code comments and set the minimum `cpuCFSQuotaPeriod` to 1ms to match Linux kernel expectations. ([#112123](https://github.com/kubernetes/kubernetes/pull/112123), [@paskal](https://github.com/paskal))

- Removed extra pod creation expectations when daemonset fails to create pods in batches. ([#74856](https://github.com/kubernetes/kubernetes/pull/74856), [@draveness](https://github.com/draveness))

            val bufferedRequestBody = exchange.createRequestBody(request, true).buffer()
            requestBody.writeTo(bufferedRequestBody)
          } else {
            // Write the request body if the "Expect: 100-continue" expectation was met.
            val bufferedRequestBody = exchange.createRequestBody(request, false).buffer()
            requestBody.writeTo(bufferedRequestBody)
            bufferedRequestBody.close()
          }
        } else {