Forum Discussion

jkrolczy's avatar
jkrolczy
Regular Contributor
3 years ago
Solved

TestComplete 14: Execution by command line: Passing in /PrjVar:NwkENV=QA01 stopped working

TestComplete 14: Execution by command line: Passing in /PrjVar:NwkENV=QA01 stopped working and is not being recognized as it should be.   I have an ADO pipeline setup to pass in a command line to ...
Command Line
Desktop Testing
Test Run
Variables
Web Testing
  • Marsha_R's avatar
    Marsha_R
    3 years ago

    My automation relies on the ability to pass in a value to set the Project Variable NwkENV so the test script

    runs on the correct environment - how script code is designed.

     

    Yes, I understand that, but in troubleshooting a problem, one wants to go to the basics first.  If the test doesn't run inside TestComplete, then troubleshooting at the higher level does no good. 

     

    Project.Variables.NwkENV = 'QA01'; 

    (If manually added in the script, this would allow the script to run -  mimicking if the command line had worked and set the Project Variable  NwkENV=QA01)

     

    Thank you for checking that the test does still run inside TestComplete.

     

    Since nothing changed in your system, I think you'll still need to contact Support directly at the link I posted.  They may have already encountered this issue with someone else and have a ready answer.

     

     

Marsha_R's avatar
Marsha_R
Champion Level 3

My automation relies on the ability to pass in a value to set the Project Variable NwkENV so the test script

runs on the correct environment - how script code is designed.

 

Yes, I understand that, but in troubleshooting a problem, one wants to go to the basics first.  If the test doesn't run inside TestComplete, then troubleshooting at the higher level does no good. 

 

Project.Variables.NwkENV = 'QA01'; 

(If manually added in the script, this would allow the script to run -  mimicking if the command line had worked and set the Project Variable  NwkENV=QA01)

 

Thank you for checking that the test does still run inside TestComplete.

 

Since nothing changed in your system, I think you'll still need to contact Support directly at the link I posted.  They may have already encountered this issue with someone else and have a ready answer.

 

 

jkrolczy's avatar
jkrolczy
Regular Contributor
3 years ago

Thanks Marsha