Inicie o servidor Fess e execute o seguinte comando:

    $ mvn test -P integrationTests -Dtest.fess.url="http://localhost:8080" -Dtest.search_engine.url="http://localhost:9201"

Para executar um único caso de teste, você pode usar:

    $ mvn test -P integrationTests -Dtest.fess.url="http://localhost:8080" -Dtest.search_engine.url="http://localhost:9201" -Dtest=SearchApiTests

### Traduzir para o Seu Idioma

  # Unpacking a wheel creates a directory named
  # {distribution}-{version}.dist-info which contains the metadata files. We
  # replace the old tag in the WHEEL file in this directory with the new tag we
  # have in ${whl_tag}. Replace the line in WHEEL that starts with "Tag:" with
  # "Tag: <new whl tag>"
  sed -i "s/^Tag:.*/Tag: ${whl_tag}/g" "${pkg_name}"/"${pkg_name}".dist-info/WHEEL

    public Integer size;

    /** Minimum document count required for a facet value to be included */
    public Long minDocCount;

    /** Sort order for facet values (e.g., "count.desc", "term.asc") */
    public String sort;

    /** Value to use for documents that don't have the facet field */
    public String missing;

    /**
     * Default constructor for FacetInfo.
     */

API changes
-----------

We make changes to Guava's public [APIs][], including adding new APIs, very
carefully. Because of this, if you're interested in seeing a new feature in
Guava, the best approach is to create an [issue][] (or comment on an existing
issue if there is one) requesting the feature and describing specific use cases
for it.

If the feature has merit, it will go through a thorough process of API design

    - [Server binaries](#server-binaries-3)
    - [Node binaries](#node-binaries-3)
  - [Changelog since v1.18.16](#changelog-since-v11816)
  - [Changes by Kind](#changes-by-kind-3)
    - [Failing Test](#failing-test)
    - [Bug or Regression](#bug-or-regression-3)
  - [Dependencies](#dependencies-3)
    - [Added](#added-3)
    - [Changed](#changed-3)
    - [Removed](#removed-3)
- [v1.18.16](#v11816)

  #   title: Learn to build high-quality web apps with best practices
  #   img: https://fastapi.tiangolo.com/img/sponsors/testdriven.svg
  - url: https://lambdatest.com/?utm_source=fastapi&utm_medium=partner&utm_campaign=sponsor&utm_term=opensource&utm_content=webpage
    title: LambdaTest, AI-Powered Cloud-based Test Orchestration Platform

			Code:           "XMinioStorageVersionMismatch",
			Description:    desc,
			HTTPStatusCode: http.StatusUpgradeRequired,
		}, r.URL)
	case strings.HasPrefix(r.URL.Path, adminPathPrefix):
		var desc string
		version := extractAPIVersion(r)
		switch version {
		case "v1", madmin.AdminAPIVersionV2:

						</la:option>
						<la:option value="last_modified.desc">
							<la:message key="labels.search_result_sort_last_modified_desc" />
						</la:option>
						<c:if test="${searchLogSupport}">
							<la:option value="click_count.asc">
								<la:message key="labels.search_result_sort_click_count_asc" />
							</la:option>
							<la:option value="click_count.desc">

	</dd>
	<dt>정렬</dt>
	<dd>
		sort 연산자는 지정된 필드 이름으로 문서를 정렬합니다.
		sort 연산자의 사용 방법은 sort:&lt;field&gt;.&lt;order&gt;입니다.
		&lt;order&gt; 는 asc 또는 desc 오름차순 · 내림차순을 지정할 수 있습니다.
		예를 들어, Fess를 포함한 문서 크기의 내림차순으로 정렬하려면 다음과 같이 입력합니다.
		<pre>Fess sort:content_length.desc</pre>
		기본으로 사용 가능한 필드는 created, content_length 및 last_modified됩니다.
		설정에서 지정하는 필드는 변경할 수 있습니다.
	</dd>
	<dt>AND검색</dt>
	<dd>
		AND 연산자는 선택적 연결 연산자입니다.

          branch-suffix: timestamp
          delete-branch: true
          title: 'Update performance test durations'
          signoff: true
          sign-commits: true
          labels: |
            in:building-gradle
            @dev-productivity
          body: |