Forum Discussion

rwood_cert's avatar
rwood_cert
Occasional Contributor
9 months ago
Solved

TestComplete Test Adapter (v15.53.9) issues running tests in DevOps

Hi,

 

We're currently seeing issues running our tests via TestExecute, we believe this is being caused/coincided with the update to the TestComplete test adapter yesterday as our tests were completely fine on the evening of the 25th July, we run tests daily, with tests on the 26th July failing after the new version of the test adapter was released.

 

I've listed a snippet of the build log as below;

 

"2023-07-27T08:49:29.7207073Z ##[error]Failed to get a list of tests from the "C:\a\r1\a\<REPONAMERemoved>\<FileName>.pjs" file due to the following error: Cannot start process because a file name has not been provided.
2023-07-27T08:49:29.7214527Z No test matches the given testcase filter `Group=InstallationAndLicencing` in C:\a\r1\a\<REPONAMERemoved>\<FileName>.pjs
2023-07-27T08:49:29.7950327Z Results File: C:\a\_temp\TestResults\AzDevOps_UIMCUKP0002RD_2023-07-27_08_49_29.trx
2023-07-27T08:49:29.8173580Z ##[error]Test Run Failed."

 

In an attempt to rule out any issues our side, we've updated to the latest version of TestExecute that we can download, v15.53.2 and installed this on the VM image that gets installed on our VMSS, but not change.

 

Is there some other modification we're required to do? 

Or is there an issue within the test adapter within DevOps - https://marketplace.visualstudio.com/items?itemName=SmartBearSoftware.install-testcomplete-adapter-task&ssr=false#overview

 

Thanks

Test Run
  • PMularczyk's avatar
    PMularczyk
    9 months ago

    Hey,

     

    we just released new version of Test Adapter.

     

    Best regards,

    Pawel

42 Replies

Sort By
  • PMularczyk's avatar
    PMularczyk
    Staff
    9 months ago

    Hey everyone,

    Quick update from our side - the problem has been fixed by our developer, at the moment we are testing the fixes and tomorrow we are planning a release.

    Best regards,

    Pawel

    • sbergot's avatar
      sbergot
      Occasional Visitor
      9 months ago

      Thank you for the update.

       

      tomorrow we are planning a release.

       

      does that mean that there will be a release today or that or are deciding on a future date today?

      Can you comment on why a rollback hasn't been published for the classic pipeline task? It has been more than a week without the possibility to run the tests.

  • nandini_thota's avatar
    nandini_thota
    Contributor
    9 months ago

    Hi,

     

    We're also seeing same issue while running our tests today. It was working fine a couple of days ago and I am getting this error while running today.

     

     

    • Per-Erik_Ek's avatar
      Per-Erik_Ek
      New Contributor
      9 months ago

      +1. We've the same issue. Appeared yesterday evening. 

      Error message: Cannot start process because a file name has not been provided.

       

      Previous version (1.15040.421) of the test adapater was able to run our tests.

  • SlickRick's avatar
    SlickRick
    Contributor
    9 months ago

    Honestly im not too sure how come they have not rollback their task to the previous version until they debug it.

    AlexKaras : was there any update on the support ticket?

    • AlexKaras's avatar
      AlexKaras
      Champion Level 3
      9 months ago

      SlickRick :

       

      > was there any update on the support ticket?

      Nothing really significant. Just several acknowledgements that they received initial and additional information from me and are investigating the case.

       

      > how come they have not rollback their task to the previous version

      Seems to be the easiest and non-breaking remediation action... Hopefully, we are not aware about why this cannot be done.

       

  • asharijaz's avatar
    asharijaz
    Staff
    9 months ago

    Please uninstall TestExecute and reinstall it in the following folder it will work.

     C:\Program Files (x86)

     

    That's the only work around which we have at the moment

    • SlickRick's avatar
      SlickRick
      Contributor
      9 months ago

      asharijaz Test execute was already installed at that location.

      Nevertheless, I still try to uninstall and reinstall at that location but I'm still facing the issue.

      Starting to get a bit impatient here as my whole production is on hold...

  • PMularczyk's avatar
    PMularczyk
    Staff
    9 months ago

    Hey,

     

    we just released new version of Test Adapter.

     

    Best regards,

    Pawel

    • rwood_cert's avatar
      rwood_cert
      Occasional Contributor
      9 months ago

      Can confirm this latest version of the DevOps test adapter does resolve the issue we originally had.

       

      It works in combination with TE v15.48, our testers had to roll back to this version as having issues with anything v15.51+, but this is an issue prior to test adapter issue

      • dhundley's avatar
        dhundley
        Regular Contributor
        9 months ago

        if i understand it correctly, they're not talking about a new version of testcomplete/testexecute but rather a new version of the testcomplete adapter on the azure (in my case) marketplace. in other words this:

         

         

  • michalforgusion's avatar
    michalforgusion
    New Member
    9 months ago

    When running tests in DevOps (probably Microsoft Azure DevOps) and having problems with the TestComplete Test Adapter (v15.53.9), it's important to explore step by step to find and fix the problems. Here are some general ways to deal with the problems:

    1. Check Compatibility: Make sure that the version of TestComplete Test Adapter you are using is compatible with the version of TestComplete you have loaded. Compatibility problems can sometimes cause people to act in strange ways.

    2. Installing and setting it up:
    Make sure the TestComplete Test Adapter is installed and set up properly in your Azure DevOps environment. Check the settings again, such as the path to the TestComplete executable and any other important setup settings.

    3. Building and deploying:
    Make sure that your build and deployment pipeline includes your test project and any TestComplete files and tools that it needs. Make sure that the right things are being copied to the right places.

    4. **Environment of the agent:**
    If you're running the tests with agents, make sure the agent setup is set up correctly. Check that TestComplete has all of the dependencies and permissions it needs to work properly.

    5. Logs of how tests were run:
    In Azure DevOps, look at the logs that are made when tests are run. These logs can tell us a lot about any mistakes or problems that came up during the test run.

    6. Messages of error:
    Pay close attention to any problem messages or warnings that come up while running the test. These messages can often help you figure out what's wrong and how to fix it.

    7. Questions about the path and file:
    Make sure that all of the file paths and references in your test project are correct and can be reached from the area where the project is built and deployed. Problems with file names can make it impossible to run a test.

    8. Licences for TestComplete:
    Make sure that the TestComplete licences in the locations where you want to run the tests are valid and turned on. Licence problems can make it so that TestComplete can't run tests.

    Permissions for the agent: Make sure that the user or service account that is running the agent has the rights to access the TestComplete installation and any other related resources.

    10. Connectivity to the network:
    If your tests involve network interactions, make sure that the test environment has the necessary network connection and access to external resources.

    11. Add-ons for Azure DevOps:
    Check to see if the TestComplete Test Adapter add-on for Azure DevOps has any changes or patches. Known problems might be fixed by installing the latest version.

    12. The community and help:
    If you've taken the steps above and are still having trouble, you could ask for help in the TestComplete community forums or through SmartBear, the company that makes TestComplete. Depending on your position, they might be able to help you in a certain way.

    Keep in mind that fixing integration problems can be hard, and it's important to get as much information as you can to find the cause.

    • D0UG's avatar
      D0UG
      Community Manager
      9 months ago

      AlexKaras thanks for flagging. I've checked with our support team and will report back when I have some answers.

      • SlickRick's avatar
        SlickRick
        Contributor
        9 months ago

        D0UG : Any updates? 

        I don't want to be annoying, but this is a pretty critical issue. Currently none of our build works and we are currently setting up our build infrastructure. We paused because of this.

        Please rollback the task to the previous version that was working.

        Thank you.

  • jrsbr's avatar
    jrsbr
    Contributor
    9 months ago

    We're getting the same.  Needs sorting quickly.

  • dhundley's avatar
    dhundley
    Regular Contributor
    9 months ago

    i am getting this also. would going back to the previous version of testexecute resolve it, at least, temporarily until it can be fixed?

     

  • dhundley's avatar
    dhundley
    Regular Contributor
    9 months ago

    my Azure pipelines are running successfully now. i'm am no longer getting the "Cannot start process because a file name has not been provided." error message. the only change I made was to ensure TestExecute is active before the pipeline kicks off. Before, TextExecute was not actively running on the VM (which is the way I've had it set up for almost a year) and the pipeline would start TE, run the test scripts and then exit TE when the pipeline completed. something has changed in the latest release(s) that seems to have altered that feature. Can anyone else confirm this as a solution?

     

    • dhundley's avatar
      dhundley
      Regular Contributor
      9 months ago

      just to add one thought to this, at our company i can probably get away with leaving TestExecute active 24x7 because we have a sufficient number of licenses for me to do that but for anyone who has multiple developers sharing licenses it's beneficial to not leave it active all the time. that's tying up a license when it's not really being used. 

    • SlickRick's avatar
      SlickRick
      Contributor
      9 months ago

      Sadly this solution would not work for me since i need to pass some variables to TestExecute using /Pvar. 

      This only seems to work when testexecute is not already running.

      • dhundley's avatar
        dhundley
        Regular Contributor
        9 months ago

        i understand. still curious if anyone else (who doesn't have that need) could confirm that something has been changed in recent releases (i installed 15.52 and experienced the same behavior) that is preventing an Azure pipeline from starting and ending testexecute using the classic editor? are there new fields that have to be set or something? or is this a bug that will be fixed in the next release so i can go back to how mine was before?

    • dhundley's avatar
      dhundley
      Regular Contributor
      9 months ago

      i just returned from vacation to discover that none of my automated testcomplete pipelines will run EVEN WHEN testexecute is actively running on the VM (see my post from 7/28). now, with TE running,  i'm seeing  this error 

       

      Unable to connect to TestExecute: it is running with different rights, or its state is incorrect. Please close it and try again.

       

      i have tried closing and restarting testexecute both normally and running as admin but nothing works.

       

      when is that new release available? if not today, then which previous version does work?

       

      Given the recent fiasco with the Chrome and Edge browsers and now this, i'm beginning to regret the recommendation i made to the management at my company to abandon Ranorex in favor of TestComplete. What is it with SmartBear lately that is causing all these show stopping issues to occur?