Forum Discussion

enriquebravo's avatar
enriquebravo
Contributor
2 years ago
Solved

Azure Pipeline Does Not Run Selected Tests

Hello everyone,   There are several moving parts that may be affecting this but I will try to keep it as simple as I can.   I created a basic keyword test that launches and closes Chrome. The tes...
Integrations
Keyword Tests
Web Testing
  • enriquebravo's avatar
    enriquebravo
    2 years ago

    Hello... sorry this is coming until now.

     

    Just for reference for whoever encounters a similar issue. The root problem was the user with which the Azure agent was setup. Initially, the Azure agent was setup using the credentials of a member of the Infrastructure team. Then, I would log in with another user account which also had admin privileges. I was under the impression that this would make services available as they were for the user who setup the agent, but that was not the case. The Azure listener was conflicting and not launching automatically when I logged in with the user that would run the scripts. This also, had a side-effect on the TestExecute execution, etc.

     

    The solution was to rerun the Azure agent setup, this time with the user that would be executing the tests and things look better now. Another related hint is that in the Visual Studio task I was including the "@" symbol as part of the filter, and that is not supposed to be included.

     

    Thanks all for putting some time into finding a solution.

     

    Best,

     

    Enrique

Kitt's avatar
Kitt
Regular Contributor

What happens if you use TestComplete as your preferred test runner?

 

Assuming you have followed the TestComplete tagging reference [here] ? You can test locally on the machine the pipeline run on by opening up command-line and using something like this to test: TestComplete.exe project-suite-file /project:project-name /test:"@azure" /run

 

enriquebravo's avatar
enriquebravo
Contributor
2 years ago

Hello... sorry this is coming until now.

 

Just for reference for whoever encounters a similar issue. The root problem was the user with which the Azure agent was setup. Initially, the Azure agent was setup using the credentials of a member of the Infrastructure team. Then, I would log in with another user account which also had admin privileges. I was under the impression that this would make services available as they were for the user who setup the agent, but that was not the case. The Azure listener was conflicting and not launching automatically when I logged in with the user that would run the scripts. This also, had a side-effect on the TestExecute execution, etc.

 

The solution was to rerun the Azure agent setup, this time with the user that would be executing the tests and things look better now. Another related hint is that in the Visual Studio task I was including the "@" symbol as part of the filter, and that is not supposed to be included.

 

Thanks all for putting some time into finding a solution.

 

Best,

 

Enrique