Why Does My Taurus Test Work Locally But Not in BlazeMeter?

There are various reasons why a Taurus script that is working locally fails to run through BlazeMeter. Inspect the failed result and check the log file to identify the issues.

Some of the common scenarios when a locally successful test fails to run in BlazeMeter are as follows:

• You have not uploaded all the required data files alongside the Taurus script in BlazeMeter.
• The Taurus script includes an absolute path to a local CSV file in the YML file. Replace it by a relative path.
• You did not specify the "locations" parameter (followed by a cloud location) in the YAML file.
  To get the list of available locations, run the following command:
  bzt -locations -o modules.cloud.token=<API Key>
• You did not specify "provisioning: cloud" when running the Taurus script from the command line. There is, however, no need to specify it when running the test from BlazeMeter UI.