Closed salmankhwaja closed 4 years ago
I have the same issue..
our variables are not being transformed into values from TFS Builds to Gauge environment and ultimately in program.
Can you give an example of how you are trying to access environment variables?
I have put the %{variable} in Scenario of Spec file.
Example :
This is a scenario that starts OWASP ZAP
Want to replace the "login_page_url" with the variable provide through TFS during build.
This is not supported at the moment on specs. You can access the environment variable in the step implementation for example in Java
@Step("Start ZAP and Open URL")
public void startZap() {
String url = System.getenv("login_page_url");
...
}
@salmankhwaja is this the same issue that you are facing too?
There's a discussion about this here https://github.com/getgauge/gauge/issues/1395
@zabil ,
Thanks. Yeah I was having the same problem.
Hi,
We are integrating Gauge with TFS Builds. We have successfully ran gauge with OWASP Zap. When we are implementing Gauge with TFS using TFS Build variables, our variables are not being transformed into values from TFS Builds to Gauge environment and ultimately in program.
Please provide help if you know.
Environment details:
Windows 2012, Command line. TFS is on Windows Also Agent is on Windows also.
Gauge is running with windows, python, and OWASP ZAP.