Documentation

Statements

A statement controls execution.

Statement      = [ Attributes ] StatementInner .
StatementInner = OptionAssignment
                | BuiltinStatement
                | VariableAssignment
                | ReturnStatement
                | ExpressionStatement
                | TestcaseStatement .

Return statements

A terminating statement prevents execution of all statements that appear after it in the same block. A return statement is a terminating statement.

ReturnStatement = "return" Expression .

Expression statements

An expression statement is an expression where the computed value is discarded.

ExpressionStatement = Expression .
Examples of expression statements
1 + 1
f()
a

Testcase statements

A testcase statement defines a test case.

Testcase statements only work within the context of a Flux development environment.

TestcaseStatement = "testcase" identifier [ TestcaseExtention ] Block .
TestcaseExtention = "extends" string_lit

Test cases are defined as a set of statements with special scoping rules. Each test case statement in a file is considered to be its own main package. In effect, all statements in package scope and all statements contained within the test case statement are flattened into a single main package and executed. Use the testing package from the standard library to control the pass failure of the test case.

Test extension augments an existing test case with more statements or attributes. A special function call, super(), must be made inside the body of a test case extension. All statements from the parent test case will be executed in its place.

Basic testcase for addition
import "testing"

testcase addition {
    testing.assertEqualValues(got: 1 + 1, want: 2)
}
Example testcase extension to prevent feature regression
@feature({vectorization: true})
testcase vector_addition extends "basics_test.addition" {
    super()
}

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2