Forum Discussion

mortenb123's avatar
mortenb123
Contributor
6 years ago

TestExecute upgraded, but all I get is "You cannot run CrossBrowserTesting tests in TestExecute."

Tests runs fine in TC14.2, also ran fine in TE11.20, but after upgrade I get the above message. I'm testing a Desktop project, but during installation it asked to upgrade Chrome and Gecko drivers and...
  • mortenb123's avatar
    mortenb123
    6 years ago

    Thanks, after looking this up, I believe storages.INI it the cleanest way to solve this.

    I also have a deploy.py script that parses the setupfile and replace it with the correct values.

     

    Thanks again

mortenb123's avatar
mortenb123
Contributor
6 years ago

I get it to work if I start TestExecute and use the GUi to load and then Run, but I have no control with the environment settings I need. So it starts and fails, so it means there must be something with the parameters.

 

I can run the following, but how can I control my own variables I need to enclose like /lrapath, /lrapathlocal /lrapathbuypass and \lrapathmixed? is it possible to add a json or xml file with this?

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    6 years ago

    Those commandline switches are not recognized by TestExecute or TestComplete.  There is no way, without code, to have the automation recognize those switches.  You can write custom code to read the commandline of TestExecute, find the switches, and operate against them.  I've done it so I know it works.

     

    Alternatively, rather than commandline switches, considering using Storages.INI to create an INI file that contains custom values like this.

    • mortenb123's avatar
      mortenb123
      Contributor
      6 years ago

      Thanks, after looking this up, I believe storages.INI it the cleanest way to solve this.

      I also have a deploy.py script that parses the setupfile and replace it with the correct values.

       

      Thanks again

      • mortenb123's avatar
        mortenb123
        Contributor
        6 years ago

        We found that the parameter /environmentwas the culprit. We renamed it and then it works fine again.

Related Content