When i run this command, it starts the TestExecute and starts running the test but it does not invoke my applcation inr.exe which is in C:\ADOAgent\vsts-agent-win-x64-2.181.2_1\_work\r1\a\_inr\inr Binaries\inr.exe location.
I believe it has something to do with the /arg command it is not able to find my Test Complete project. this is what i read in the below link -:
What the arg is meant to do is pass in that value (your .exe location) to a TestComplete argument (your inrExeLocation). The arg itself is not going to invoke anything. You have to use the InrExeLocation somehow inside your test to do the invoking.
Note that this says "test parameters". The /arg in the Session Creator call is not an argument for Session Creator to use. It is an argument that you are passing into your TestComplete project (which is your actual test code) for TestComplete to use.
I am just confused how will i use BuiltIn.ParamCount and BuiltIn.ParamsStr methods in TestComplete because when i specifiy inrexelocation in the script.
Currently i have a variable in testcomplete which is called "inrexelocation" and it points to the path i have specified in the script but it does not invoke the applications...so somehow i have to use Buildin.Paramcount and bBuiltin.Paramstr to invoke it. Not sure how i will handle that 😞
I was able to get the SessionCreator working but there seems to be another issue which cropped up.
I am using SessionCreator with Azure DevOps pipeline using Powershell task and to publish the results in the "Test" tab i am using another task called "Publish Test Results" which should publish the .XML file but it does not seem to publish the results in the "Test" Tab. It gives me a message saying
"No Result Found to Publish 'C:\ADOAgent\vsts-agent-win-x64-2.181.2_1\_work\r5\a\_INR-TestAutomation\Test-logs.xml"
Seems like I have fixed the issue with Test Results not being published. Now it shows the results in the "Test" tab.
However, now I want to run SessionCreator.exe using local user account and not the domain account.
so, when I try to run using the local user account from the pipeline, I am getting the below error -:
SessionCreator.exe : The term 'SessionCreator.exe' is not recognized as the name of a cmdlet
do you know how can I get around this problem?
I am also getting the same error when I login to the VM using local user account and run it directly through PowerShell as administrator. However, when I run the TestExecute first and then run SessionCreator.exe it runs fine which is wierd.
Not sure how can i make it run through the Azure DevOps Pipeline.