Skip to content

Implement "strict mode" where referencing an undefined variable in ${nonExistingVar} would fail #6025

@vlsi

Description

@vlsi

Use case

Currently, a typo in variable name is hard to spot as it might silently pass to the downstream system unnoticed.

Possible solution

It might be helpful if we implement opt-in "strict mode" so referencing unknown variables becomes error rather than acceptable behavior.

See:

Possible workarounds

No response

JMeter Version

5.6

Java Version

No response

OS Version

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions