elasticsearch/docs/reference/modules/scripting
Nik Everett 4b1c116461 Generate and run tests from the docs
Adds infrastructure so `gradle :docs:check` will extract tests from
snippets in the documentation and execute the tests. This is included
in `gradle check` so it should happen on CI and during a normal build.

By default each `// AUTOSENSE` snippet creates a unique REST test. These
tests are executed in a random order and the cluster is wiped between
each one. If multiple snippets chain together into a test you can annotate
all snippets after the first with `// TEST[continued]` to have the
generated tests for both snippets joined.

Snippets marked as `// TESTRESPONSE` are checked against the response
of the last action.

See docs/README.asciidoc for lots more.

Closes #12583. That issue is about catching bugs in the docs during build.
This catches *some* bugs in the docs during build which is a good start.
2016-05-05 13:58:03 -04:00
..
advanced-scripting.asciidoc Reorganise scripting docs (#18132) 2016-05-04 18:17:10 +02:00
expression.asciidoc docs: remove null from expressions case. 2016-05-04 12:50:12 -04:00
fields.asciidoc Reorganise scripting docs (#18132) 2016-05-04 18:17:10 +02:00
groovy.asciidoc Reorganise scripting docs (#18132) 2016-05-04 18:17:10 +02:00
native.asciidoc Reorganise scripting docs (#18132) 2016-05-04 18:17:10 +02:00
painless.asciidoc Generate and run tests from the docs 2016-05-05 13:58:03 -04:00
security.asciidoc Reorganise scripting docs (#18132) 2016-05-04 18:17:10 +02:00
using.asciidoc Generate and run tests from the docs 2016-05-05 13:58:03 -04:00