All Classes and Interfaces

Class
Description
Represents a test fragment that contains the information needed to call an api
Base class for executable sections that hold assertions
Used to execute REST requests according to the docs snippets that need to be tests.
Specification of an Elasticsearch endpoint used by the YAML specs to generate REST requests.
 
 
 
 
Holds the specification used to turn do actions in the YAML suite into REST api calls.
Wraps ClientYamlTestSections ready to be run.
Used by ESClientYamlSuiteTestCase to execute REST requests according to the tests written in yaml suite files.
Execution context passed across the REST tests.
Response obtained from a REST call, eagerly reads the response body into a string for later optional parsing.
Exception obtained from a REST call in case the response code indicated an error.
Represents a test section, which is composed of a skip section and multiple executable sections.
Holds a REST test suite loaded from a specific yaml file.
Represents a close_to assert section: - close_to: { get.fields._routing: { value: 5.1, error: 0.00001 } }
 
Represents a do section: - do: catch: missing headers: Authorization: Basic user:pass Content-Type: application/json warnings|warnings_regex: - Stuff is deprecated, yo - Don't use deprecated stuff - Please, stop.
Runs a suite of yaml tests shared with all the official Elasticsearch clients against an elasticsearch cluster.
Represents a test fragment that can be executed (e.g.
Represents an exists assert section: - exists: get.fields.bar
Allows to register additional features supported by the tests runner.
Represents a gt assert section:
Represents a gte assert section: - gte: { fields._ttl: 0 }
Impersonates an official test client by setting the @{code x-elastic-client-meta} header.
Represents an is after assert section: - is_after: { result.some_instant: "2023-05-25T12:30:00.000Z" }
Represents an is_false assert section: - is_false: get.fields.bar
Represents an is_true assert section: - is_true: get.fields.bar
Represents a length assert section:
Represents a lt assert section: - lt: { fields._ttl: 20000}
Represents a lte assert section: - lte: { fields._ttl: 0 }
Represents a match assert section: - match: { get.fields._routing: "5" }
Represents an exists assert section:
a wrapper around YamlXContentParser that allows for parameter replacement in the yaml file
 
Represents a section where prerequisites to run a specific test section or suite are specified.
Represents a set section: - set: {_scroll_id: scroll_id}
Represents a setup section.
 
Represents a transform_and_set section: