JMeter中读取与删除对象时token变量传参失效问题咨询

Hey there, let's troubleshoot why your token variable isn't being picked up in the DELETE request—even though the Debug Sampler shows it's correctly set. I've dealt with this exact issue before, so here are the most common fixes to try:

1. Check Variable Scope #

JMeter variables have thread/controller-specific scopes, which might be blocking your DELETE request from accessing the token.

• Same Thread Group: Ensure the GET request runs before the DELETE request. JMeter executes elements top-to-bottom by default, so double-check your test plan order. If you're using controllers (like Loop Controller), make sure both requests are in the same controller scope.
• Cross Thread Groups: If your GET and DELETE are in different thread groups, use global properties instead of local variables. Add a JSR223 PostProcessor to the GET request with this code:

  props.put("global_token", vars.get("token"))
  

  Then reference it in the DELETE request as ${__P(global_token,)}.

2. Verify Variable Reference Syntax #

It's easy to make a small typo that breaks the variable reference:

• Ensure you're using the correct syntax: ${token} (replace "token" with your actual variable name).
• Check for typos (e.g., ${tokenn} instead of ${token}) or missing curly braces (using token instead of ${token}).
• If using the token in a JSON payload, make sure it's properly formatted without extra quotes:

  {"auth_token": "${token}"}
  

3. Confirm CSV & Execution Order #

If your CSV file lists DELETE requests before their corresponding GETs, JMeter will try to run the DELETE first (before the token is fetched):

• Reorder your CSV rows so GET requests come before their matching DELETEs.
• Use a Sequence Controller to wrap the GET and DELETE requests—this forces the GET to execute first every time, regardless of CSV order.

4. Ensure Token is Set Before DELETE Runs #

Even if the Debug Sampler shows the token, there might be a silent failure or timing issue:

• Add a Response Assertion to the GET request to verify it returns a 200 OK status code and that the token exists in the response body.
• Add a JSR223 PreProcessor to the DELETE request to log the token value right before execution:

  log.info("Token for DELETE request: " + vars.get("token"))
  

  Check the JMeter logs to see if the variable is null or holds the correct value when the DELETE runs.

5. Validate Token Extraction Configuration #

Double-check the extractor you're using to capture the token from the GET response:

• JSON Extractor: Confirm the "Reference Name" matches your variable name, the "JSON Path Expression" is correct (e.g., $.data.token), "Match No." is set to 1 (to grab the first occurrence), and "Default Value" is set to something like "TOKEN_NOT_FOUND" to debug extraction failures.
• Regular Expression Extractor: Make sure your regex correctly captures the token (e.g., "token":"(.+?)"), the "Template" is $1$ (to use the captured group), and "Match No." is 1.

Try these steps one by one—chances are it's a simple scope, syntax, or order issue. Let me know if any of these resolve your problem!

内容的提问来源于stack exchange，提问作者Vittal