import okhttp3.OkHttpClient
import okhttp3.Request

class PostForm {
  private val client = OkHttpClient()

  fun run() {
    val formBody =
      FormBody
        .Builder()
        .add("search", "Jurassic Park")
        .build()
    val request =
      Request(
        url = "https://en.wikipedia.org/w/index.php".toHttpUrl(),
        body = formBody,
      )

    client.newCall(request).execute().use { response ->

      ),
    )
  }

  @Test
  fun `certificate attributes`() {
    val certificate =
      HeldCertificate
        .Builder()
        .certificateAuthority(3)
        .commonName("Jurassic Park")
        .organizationalUnit("Gene Research")
        .addSubjectAlternativeName("*.example.com")
        .addSubjectAlternativeName("www.example.org")
        .validityInterval(-1000L, 2000L)
        .serialNumber(17L)

<module>
<source path="">
  <!-- Hack to keep collect from hiding collect.testing supersource: -->
  <exclude name="**/testing/**"/>
</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see

        assertFalse(searchRenderData.isExistNextPage());

        // Test with true
        searchRenderData.setExistNextPage(true);
        assertTrue(searchRenderData.isExistNextPage());

        // Toggle back to false
        searchRenderData.setExistNextPage(false);
        assertFalse(searchRenderData.isExistNextPage());
    }

    public void test_setAndIsExistPrevPage() {
        // Test with false

  }

  /*
   * TODO(b/242884182): Figure out why this helps produce the same class file when we compile most
   * of common.collect a second time with the results of the first compilation on the classpath. Or
   * just back this out once we stop doing that (which we'll do after our internal GWT setup
   * changes).
   */
  @Override
  public ImmutableMap<Object, Collection<Object>> asMap() {
    return super.asMap();
  }

    @Test
    void testConstructorWithUserInfoNoDomain() {
        NtlmPasswordAuthentication auth = new NtlmPasswordAuthentication("user:password");
        assertNotNull(auth.getDomain()); // Should fall back to default
        assertEquals("user", auth.getUsername());
        assertEquals("password", auth.getPassword());
    }

    // Test constructor with user info string without password
    @Test

                "The 'next' property of the initial referral should point to the appended referral.");
        assertEquals(initialReferral, appendedReferral.next,
                "The 'next' property of the appended referral should point back to the initial referral, closing the loop.");
    }

    /**
     * Tests the toString method of the DfsReferral class.
     * It verifies that the toString method returns a string representation of the object

<module>
<source path="">
  <!-- Hack to keep collect from hiding collect.testing supersource: -->
  <exclude name="**/testing/**"/>
</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see

<module>
<source path="">
  <!-- Hack to keep collect from hiding collect.testing supersource: -->
  <exclude name="**/testing/**"/>
</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see

<module>
<source path="">
  <!-- Hack to keep collect from hiding collect.testing supersource: -->
  <exclude name="**/testing/**"/>
</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see