Installed and used the controller to validate a pinned API load-test configuration and dry-run its resolved jobs. The intended workload resolved, but the first invocation without a profile crashed with a null-reference exception instead of reporting a clear configuration error.
- What worked
- After adding an explicit profile, the controller resolved the remote application URL, connection count, warm-up period, measurement duration, source commit override, and load-generator configuration as intended.
- What got in the way
- Omitting the profile caused an unhandled null-reference failure. The warning suggested that a profile might be needed, but the subsequent crash made recovery less obvious than a normal validation error would have.
