8000 User variable not resolved · Issue #25 · Blazemeter/CorrelationRecorder · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
User variable not resolved #25
Open
@plo750

Description

@plo750

I have defined a user variable PROJECT_HOME in the "User Defined Variables" element.

The PROJECT_HOME variable contains this code:

${__BeanShell(import org.apache.jmeter.services.FileServer; FileServer.getFileServer().getBaseDir();)}

After that, I reuse it in the "CSV Data Set Config" element, in the filename as follow:

${__env(DATA_CONFIG,,${__eval(${PROJECT_HOME})})}/Credentials.csv

With the "HTTP(S) Test Script Recorder" the resolution of the variable PROJETC_HOME is resolved correctly, as follow:
2021-12-07 10:20:39,175 INFO o.a.j.s.FileServer: Close: D:\Projets\Load-Tests\Auto-Correlation/Credentials.csv

But with this plugin I have the following issue:
2021-12-07 10:09:08,562 INFO o.a.j.s.FileServer: Stored: ${PROJECT_HOME}/Credentials.csv

Environment

Windows 10

  • JMeter version 5.4.1
  • Correlation Recorder: latest (1.2.1)
  • Plugin Manager (if applicable)
  • Protocol version (if apply, eg: Siebel CRM IP17 & IP18)

Step to Reproduce

  1. Define the PROJECT_HOME variable as
    ${__BeanShell(import org.apache.jmeter.services.FileServer; FileServer.getFileServer().getBaseDir();)} in the config element "User Defined Variable".
  2. In the config element "CSV Data Set Config" set the "Filename" as ${__env(DATA_CONFIG,,${__eval(${PROJECT_HOME})})}/Credentials.csv
  3. Define a simple scenario
  4. Click on Start

Expected behaviour

I expected that the ${PROJECT_HOME} is resolved as D:\Projets\Load-Tests\Auto-Correlation instead of remaining as ${PROJECT_HOME}

Complementary information

none

Additional context

none

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0