When I first called the API in jMeter, the user name and password required by the API were hard-coded so that when I posted the jMeter project files to Github to share with others, these sensitive information would be easily leaked.
Later, my colleagues taught me to use CSV data set config to store user names and passwords to avoid hard coding problems.
The method is simple: create a CSV data set config in jMeter, associate it with a local file, and define two variables named username and password.
In the API call parameter maintenance interface, the username and password are no longer hard-coded. Instead, {username} is used as a placeholder.
Finally, maintain user names and passwords in a CSV file that doesn’t have to be uploaded to Github.
For more of Jerry’s original articles, please follow the public account “Wang Zixi “:
