assertEquals(expectedTime, response.getLastAccessTime());
    }

    @Test
    void testReadParameterWordsWireFormatWithData() {
        // Test reading parameter words from wire format
        response = new SmbComQueryInformationResponse(mockConfig, 0L);

        // Prepare test data
        byte[] buffer = new byte[256];
        int bufferIndex = 0;

        // Set wordCount to non-zero

        IOException exception = assertThrows(IOException.class, () -> {
            packet.readTrailerWireFormat(bais, readBuffer, 0);
        });

        assertEquals("invalid session request wire format", exception.getMessage());
    }

    @ParameterizedTest
    @MethodSource("provideNamesForWriteTest")
    @DisplayName("writeTrailerWireFormat should handle various name combinations")

        // Then - nothing should happen (empty implementation)
        verifyNoInteractions(resp);
    }

    @Test
    @DisplayName("Should read valid negotiate response from wire format")
    void testReadBytesWireFormatValid() throws Exception {
        // Given
        byte[] buffer = createValidNegotiateResponseBuffer();

        // When

#       options in "$@", and eventually passing that to Java.
#
#       Where the inherited environment variables (DEFAULT_JVM_OPTS, JAVA_OPTS,
#       and GRADLE_OPTS) rely on word-splitting, this is performed explicitly;
#       see the in-line comments for details.
#
#       There are tweaks for specific operating systems such as AIX, CygWin,
#       Darwin, MinGW, and NonStop.
#

        throw new UnsupportedOperationException();
      }

      // Mostly safe: We check contains(u) before calling successors(u), so we perform unsafe
      // operations only in weird cases like checking for an EndpointPair<ArrayList> in a
      // Graph<LinkedList>.
      @SuppressWarnings("unchecked")
      @Override
      public boolean contains(@Nullable Object obj) {

			//
			// S3 uses B-encoding (Base64) for non-ASCII-heavy metadata and Q-encoding
			// (quoted-printable) for mostly ASCII strings. Long strings are split at word
			// boundaries to fit RFC 2047’s 75-character limit, ensuring HTTP parser
			// compatibility.
			//
			// However, this splitting increases header size and can introduce errors, unlike Go’s

        assertEquals(10, item.getQueryFreq());
    }

    @Test
    public void test_parseSearchWordsWithExcludedWords() throws Exception {
        String[] words = new String[] { "　　　", "エンジン" }; // First word is whitespace only
        String[] fields = new String[] { "content" };

        SuggestAnalyzer analyzer = suggester.settings().analyzer().new DefaultContentsAnalyzer();

    Comparator<byte[]> comparator2 = UnsignedBytes.lexicographicalComparatorJavaImpl();

    /*
     * These arrays are set up to test that the comparator compares bytes within a word in the
     * correct order—in order words, that it doesn't mix up big-endian and little-endian. The first
     * array has a smaller element at one index, and then the second array has a smaller element at
     * the next.

        // UID (2 bytes)
        buffer[28] = 0x03;
        buffer[29] = 0x00;

        // MID (2 bytes)
        buffer[30] = 0x04;
        buffer[31] = 0x00;

        // Word count
        buffer[32] = 10; // 10 words = 20 bytes

        // Parameter words for transaction response
        // Total parameter count (2 bytes)
        buffer[33] = 0x00;
        buffer[34] = 0x00;

The generated code still has some **duplicated information**.

We already know that this method is related to the **items** because that word is in the `ItemsService` (taken from the tag), but we still have the tag name prefixed in the method name too. 😕

We will probably still want to keep it for OpenAPI in general, as that will ensure that the operation IDs are **unique**.