}
          else -> throw AssertionError("unsupported hashAlgorithm: ${pin.hashAlgorithm}")
        }
      }
    }

    // If we couldn't find a matching pin, format a nice exception.
    val message =
      buildString {
        append("Certificate pinning failure!")
        append("\n  Peer certificate chain:")
        for (element in peerCertificates) {

        assertEquals("", suggestItem.getText());
    }

    @Test
    public void testMultipleReadingsConversion() {
        // Test conversion of multiple readings to SuggestItem format
        String word = "multi reading";
        float boost = 1.0f;
        List<String> readings = Arrays.asList("reading1", "reading2", "reading3", "reading4", "reading5");

        assertEquals(0, trans2QueryFSInfo.readParametersWireFormat(null, 0, 0));
        assertEquals(0, trans2QueryFSInfo.readDataWireFormat(null, 0, 0));
    }

    @Test
    @DisplayName("Test complete wire format writing")
    void testCompleteWireFormatWriting() {
        trans2QueryFSInfo = new Trans2QueryFSInformation(config, FileSystemInformation.FS_SIZE_INFO);

        byte[] setupBuffer = new byte[256];

        int actualInfoLevel = SMBUtil.readInt2(buffer, 2);
        assertEquals(0x0101, actualInfoLevel); // FILE_BASIC_INFO maps to 0x0101
    }

    @Test
    @DisplayName("Test complete wire format writing")
    void testCompleteWireFormatWriting() {
        when(mockFileInfo.getFileInformationLevel()).thenReturn((byte) FileInformation.FILE_BASIC_INFO);

      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.