Through NeoLoad as-code, users can define or override a test project elements without launching a Controller. When running automated tests, this allows:
Using test scenarios previously designed with NeoLoad GUI and using code to define the context in which they are intended for launch (test duration and VUs/load profile).
Overriding settings that depend on the execution environment (development, staging, pre-production) like Server host names, Variables or SLAs.
Designing a full test (Virtual User Paths, Scenarios, SLAs) through YAML, typically for API Testing without using the Controller to design.
As-code tests are plain text files that can be managed like any source code files and can be version controlled with any version control tool that your teams or organization use (GIT, SVN, etc.).