val responseString = decompressed.body.string()
    assertThat(responseString).isEqualTo("hello zstd world")
  }

  @Test
  fun testDecompressGzip() {
    val s = "hello gzip world".encodeUtf8().gzipCompress()

    val response =
      response("https://example.com/", s) {
        header("Content-Encoding", "gzip")
      }

        Did you *actually* encounter the need for this feature in a real-world scenario, or is it
        just a feature that seems like a sensible addition to Guava?


        Before new features get added to Guava, we really want to be sure that it's for a use case
        that actually comes up in the real world. We want to hear the real-world use case so the

            // Read remaining bytes
            byte[] remaining = new byte[20];
            int remainingBytes = stream.read(remaining);
            assertEquals(8, remainingBytes); // ", World!"
            assertEquals(", World!", new String(remaining, 0, remainingBytes, "UTF-8"));
        }
    }

    }
  }

  @Test
  fun singlePart() {
    val expected =
      """
      |--123
      |
      |Hello, World!
      |--123--
      |
      """.trimMargin().replace("\n", "\r\n")
    val body =
      MultipartBody
        .Builder("123")
        .addPart("Hello, World!".toRequestBody(null))
        .build()
    assertThat(body.boundary).isEqualTo("123")

  }

  @Override public void onOpen(WebSocket webSocket, Response response) {
    webSocket.send("Hello...");
    webSocket.send("...World!");
    webSocket.send(ByteString.decodeHex("deadbeef"));
    webSocket.close(1000, "Goodbye, World!");
  }

  @Override public void onMessage(WebSocket webSocket, String text) {
    System.out.println("MESSAGE: " + text);
  }

        assertEquals("hello", DocumentUtil.encodeUrl("hello"));
        assertEquals("hello-world", DocumentUtil.encodeUrl("hello-world"));
        assertEquals("hello_world", DocumentUtil.encodeUrl("hello_world"));
        assertEquals("hello.world", DocumentUtil.encodeUrl("hello.world"));
    }

    public void test_encodeUrl_empty_and_null() {
        assertEquals("", DocumentUtil.encodeUrl(""));

        BooleanFunction<String> startsWithHello = s -> s != null && s.startsWith("hello");

        assertTrue(startsWithHello.apply("hello world"));
        assertTrue(startsWithHello.apply("hello"));
        assertFalse(startsWithHello.apply("hi world"));
        assertFalse(startsWithHello.apply(""));
        assertFalse(startsWithHello.apply(null));
    }

    public void test_method_reference() {

        Did you *actually* encounter the need for this enhancement in a real-world scenario, or does
        it just seem like a sensible behavior for the feature to have?


        Before we make significant changes to existing features in Guava, we really want to be sure
        that it's for a use case that actually comes up in the real world. We want to hear the
        real-world use case so the community can discuss and debate whether this feature is actually

  // Responses are returned in the same order that they are enqueued.
  Chat chat = new Chat(baseUrl);

  chat.loadMore();
  assertEquals("hello, world!", chat.messages());

  chat.loadMore();
  chat.loadMore();
  assertEquals(""
      + "hello, world!\n"
      + "sup, bra?\n"
      + "yo dog", chat.messages());

  // Optional: confirm that your app made the HTTP requests you were expecting.

  }

  @Test
  fun write() {
    val operator =
      FileOperator(
        randomAccessFile!!.getChannel(),
      )
    val buffer1 = Buffer().writeUtf8("Hello, World")
    operator.write(0, buffer1, 5)
    assertThat(buffer1.readUtf8()).isEqualTo(", World")
    val buffer2 = Buffer().writeUtf8("icopter!")
    operator.write(3, buffer2, 7)
    assertThat(buffer2.readUtf8()).isEqualTo("!")