### Tests

* Help me check that the PR has **tests**.

* Check that the tests **fail** before the PR. 🚨

* Then check that the tests **pass** after the PR. ✅

* Many PRs don't have tests, you can **remind** them to add tests, or you can even **suggest** some tests yourself. That's one of the things that consume most time and you can help a lot with that.

  public void testLimitExtraSeparators() {
    String text = "a,,,b,,c,d";
    Iterable<String> items = COMMA_SPLITTER.limit(2).split(text);
    assertThat(items).containsExactly("a", ",,b,,c,d").inOrder();
  }

  public void testLimitExtraSeparatorsOmitEmpty() {
    String text = "a,,,b,,c,d";
    Iterable<String> items = COMMA_SPLITTER.limit(2).omitEmptyStrings().split(text);

    response = client.get("/query_example_examples/")
    assert response.status_code == 200, response.text
    response = client.get("/header_example/")
    assert response.status_code == 200, response.text
    response = client.get("/header_examples/")
    assert response.status_code == 200, response.text
    response = client.get("/header_example_examples/")
    assert response.status_code == 200, response.text

<div style="text-align: right; margin-right: 10%;">Kabir Khan - <strong>Microsoft</strong> <a href="https://github.com/tiangolo/fastapi/pull/26" target="_blank"><small>(ref)</small></a></div>

---

"_We adopted the **FastAPI** library to spawn a **REST** server that can be queried to obtain **predictions**. [for Ludwig]_"

start, java.lang.String separator, java.lang.String end, java.lang.Iterable<? extends SelfDescribing> values) Description Description.appendText(java.lang.String text) Appends some plain text to the description. Description Description.NullDescription.appendText(java.lang.String text) Description BaseDescription.appendText(java.lang.String text) Description Description.appendValue(java.lang.Object value) Appends an arbitary value to the description. Description Description.NullDescription.appendValue(java.lang.Object...

### Documentation pour les tests

La plupart des tests sont en fait effectués par rapport aux exemples de fichiers sources dans la documentation.

Cela permet de s'assurer que :

* La documentation est à jour.
* Les exemples de documentation peuvent être exécutés tels quels.
* La plupart des fonctionnalités sont couvertes par la documentation, assurées par la couverture des tests.

  if (project.name == "android-test") return@subprojects
  if (project.name == "regression-test") return@subprojects
  if (project.name == "android-test-app") return@subprojects
  if (project.name == "container-tests") return@subprojects

  apply(plugin = "checkstyle")
  apply(plugin = "ru.vyarus.animalsniffer")
  apply(plugin = "biz.aQute.bnd.builder")

  tasks.withType<JavaCompile> {

/a/b/c  s:http h:example.org p:/a/b/c
/a/\s/c  s:http h:example.org p:/a/%20/c
/a%2fc  s:http h:example.org p:/a%2fc
/a/%2f/c  s:http h:example.org p:/a/%2f/c
\#\u03B2  s:http h:example.org p:/foo/bar f:#\u03B2
data:text/html,test#test  s:data p:text/html,test f:#test

# Based on http://trac.webkit.org/browser/trunk/LayoutTests/fast/url/file.html

# Basic canonicalization, uppercase should be converted to lowercase

And those Python files are included/injected in the documentation when generating the site.

### Docs for tests

Most of the tests actually run against the example source files in the documentation.

This helps to make sure that:

* The documentation is up-to-date.
* The documentation examples can be run as is.

    server.enqueue(MockResponse())
    assertFailsWith<IllegalArgumentException> {
      Request.Builder().method("GET", "abc".toRequestBody("text/plain".toMediaType()))
    }
  }

  @Test
  fun head() {
    server.enqueue(
      MockResponse(
        headers = headersOf("Content-Type", "text/plain"),
      ),
    )
    val request =
      Request.Builder()
        .url(server.url("/"))
        .head()