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!

AlexKaras's avatar
AlexKaras
Champion Level 3
2 years ago

Hi,

 

> It seems like passing the Variable  in the TestComplete adapter is not working

It works for sure. Well, at least it works for our pipelines.

Azure has strange and non-explainable for me concept of runtime and design-time variables.

What I would do is to add a step between Test Adapter and Run UITests steps and output the value of the Build.BinariesDirectory variable. If the value is correct, then I would pay attention if it contains spaces. Extra quotes might be required if it does.

Additionally, add debug message to test log in TestComplete and output the value of AppPath variable and again, check if it contains expected value.

 

The bottom line: your approach is a valid one and matches to what we have in our pipelines, so it definitely can be used. What you need to do is to ensure that correct expected value is passed to Test Adapter.

 

P.S. Our pipeline is in YAML format and corresponding part for Test Adapter looks like this:

      inputs:
        installExecutor: true
        updateExecutor: false
        searchMode: ProjectItems
        logsLevel: 0
        accessKey: '$(SBAK_ALK)'
        cmdLineParams: '/pv:pvClient="$(clientsToTest)"'
        preferredExecutor: TE

 

where clientsToTest variable evaluates to something like this (without quotes): 'cl1;cl2;cl3;'