Forum Discussion
Whoops, my bad... didn't notice you weren't calling it as a string. Change your internal code line to
ProjectSuite.Variables.Environment = ogreUtils.getTCCommandLineParam('env');That didn't seem to work either. I'm getting that "You cannot run Environment Manager tests in TestExecute" error message again.
- tristaanogre8 years agoEsteemed Contributor
Just out of curiousity... disable the new function for the environment parameter and remove that parameter from your powershell and try again.
What it seems to me is that there is something in your actual project suite that is attempting to run an Environment Manager set of tests. If we remove the command line parameter and associated code and still get the error, then we know we need to look elsewhere for the solution.
- nicklott8 years agoOccasional Contributor
So I disabled the environment function and removed that environment parameter from my Powershell script and it kicked off the tests and there was no Environment Manager error. So something about the environment function (or possible the parameter in Powershell) seems to be the cause of the problem.
- tristaanogre8 years agoEsteemed Contributor
Aha! That's it... There is actually a reserved commandline parameter for TestComplete/TestExecute of /environment or /env that triggers environment manager tests.
Change the parameter to something like 'testenvironment' and use that string in your javascript function.