Forum Discussion

SlickRick's avatar
SlickRick
Contributor
2 years ago

Azure Pipeline - Variables Not passed to my test

Hi all,  So I have a project suite in which I have defined a variable 'AppPath' which points to the directory where my exe is located.   In my pipeline I follow (i believe) all the steps...
Desktop Testing
Keyword Tests
Test Run
Variables
  • SlickRick's avatar
    SlickRick
    2 years ago

    I figured it out! ğŸ˜€

     

    TestExecute was opened on the build server which was failing.

     

    Therefore my pipeline was using the opened instance to run the tests (which was opened i guess with no params).

     

    By closing it, the pipeline would open a new instance with the correct parameters.

    I would suggest to have a option on the 'Enable support for testcomplete test' task to 'Force new instance' that would auto-reload the tool to ensure that the correct param are used.

     

    Thank you!

SlickRick's avatar
SlickRick
Contributor
2 years ago

Well I talked a bit too soon.

So it works on one of my build server and on another it fails.

 

On the machine that fails, the variable returns the default value, but the variable being passed to TestExecute is ok (looking at the pipeline log).

Also it seem like no param are considered on that build machine since I also have a /DoNotShowLog  tag and the log is shown on the build server after the run is done.

 

you were talking about runtime and design-time variables. How can we determine and setup which one to use?