hpsa / adm-tfs-extension Goto Github PK

Hi Guys
I am using TFS2018 and already using Automated Builds. I have a Build definition and an agent where build gets compiled and copied to different Test Machines. Code get tested here and the results get published.
Our test cases are written as a project in main code solution which also compiled.
No one told how to set up or adjust UFT in already running Builds or convert older machines to newer UFT structure. Secondary, how to create/setup pool of machines as Test clients to cater to multiple project needs.
How can we deploy and test using the same agent if you wish to do so?

Step by Step Guide is also required which can help the people like me.

Looking forward to hearing from you.

If it's a Junit / Nunit it would be nice to save that in the working directory and parse it into the VSTS tests section for better viewing and an automated report to be generated.

Not really sure where else to post this question, if there's a better place, let me know.

I've installed the HP UFT extensions on the TFS server, no problem at all doing this.

So I try to push tests during a build process. I get a complaint about the absence of the UFT_LAUNCHER capability. I don't see any documentation on how to prepare the build agent box to get this capability. I RDP into the build agent box, install UFT and the appropriate tdconnect. I run some tests manually and all is well. I restart the build agent service and still no UFT_LAUNCHER capability. I manually add the capability and point it at the C:\Program Files (x86)\HP\Unified Functional Testing\bin directory (total guess). I run my build and I get the errors at the end of this post.

The first error about not finding bin/PSModule.dll. I see where it is looking in the specified _task folder, and yes, PSModule.dll does not exist in that directory at all.

Any help on this would be greatly appreciated! I need documentation on how to get this running.

2017-10-25T15:16:18.2237535Z ##[section]Starting: RunFromALM: 2017-10-25T15:16:18.2393770Z ============================================================================== 2017-10-25T15:16:18.2393770Z Task : UFT ALM Execution 2017-10-25T15:16:18.2393770Z Description : Execute UFT tests from ALM 2017-10-25T15:16:18.2393770Z Version : 1.0.0 2017-10-25T15:16:18.2393770Z Author : 2017-10-25T15:16:18.2393770Z Help : 2017-10-25T15:16:18.2393770Z ============================================================================== 2017-10-25T15:16:18.2706285Z Preparing task execution handler. 2017-10-25T15:16:21.7238046Z Executing the powershell script: E:\devagent\Agent1\_work\_tasks\RunFromALM_a571ae7c-e100-42e1-8ced-498b46029770\1.0.0\localTask.ps1 2017-10-25T15:16:22.1456599Z ##[error]System.IO.FileNotFoundException: The specified module '\bin\PSModule.dll' was not loaded because no valid module file was found in any module directory. 2017-10-25T15:16:22.2081612Z ##[error]System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter 'Path' because it is null. 2017-10-25T15:16:22.2081612Z at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate) 2017-10-25T15:16:22.2081612Z at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext) 2017-10-25T15:16:22.2081612Z at System.Management.Automation.Interpreter.ActionCallInstruction6.Run(InterpretedFrame frame)
2017-10-25T15:16:22.2081612Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
2017-10-25T15:16:22.2081612Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
2017-10-25T15:16:22.2237861Z ##[error]System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter 'Path' because it is null.
2017-10-25T15:16:22.2237861Z at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
2017-10-25T15:16:22.2237861Z at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
2017-10-25T15:16:22.2237861Z at System.Management.Automation.Interpreter.ActionCallInstruction6.Run(InterpretedFrame frame) 2017-10-25T15:16:22.2237861Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) 2017-10-25T15:16:22.2237861Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) 2017-10-25T15:16:22.2237861Z ##[error]System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter 'Path' because it is null. 2017-10-25T15:16:22.2237861Z at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate) 2017-10-25T15:16:22.2237861Z at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext) 2017-10-25T15:16:22.2237861Z at System.Management.Automation.Interpreter.ActionCallInstruction6.Run(InterpretedFrame frame)
2017-10-25T15:16:22.2237861Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
2017-10-25T15:16:22.2237861Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
2017-10-25T15:16:22.2237861Z ##[error]System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter 'Path' because it is null.
2017-10-25T15:16:22.2237861Z at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
2017-10-25T15:16:22.2237861Z at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
2017-10-25T15:16:22.2237861Z at System.Management.Automation.Interpreter.ActionCallInstruction6.Run(InterpretedFrame frame) 2017-10-25T15:16:22.2237861Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) 2017-10-25T15:16:22.2237861Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) 2017-10-25T15:16:22.7862935Z ##[error]System.Management.Automation.CommandNotFoundException: The term 'Invoke-RunFromAlmTask' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. 2017-10-25T15:16:22.7862935Z at System.Management.Automation.CommandDiscovery.LookupCommandInfo(String commandName, CommandTypes commandTypes, SearchResolutionOptions searchResolutionOptions, CommandOrigin commandOrigin, ExecutionContext context) 2017-10-25T15:16:22.7862935Z at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String commandName, CommandOrigin commandOrigin, Nullable1 useLocalScope)
2017-10-25T15:16:22.7862935Z at System.Management.Automation.ExecutionContext.CreateCommand(String command, Boolean dotSource)
2017-10-25T15:16:22.7862935Z at System.Management.Automation.PipelineOps.AddCommand(PipelineProcessor pipe, CommandParameterInternal[] commandElements, CommandBaseAst commandBaseAst, CommandRedirection[] redirections, ExecutionContext context)
2017-10-25T15:16:22.7862935Z at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
2017-10-25T15:16:22.7862935Z at System.Management.Automation.Interpreter.ActionCallInstruction6.Run(InterpretedFrame frame) 2017-10-25T15:16:22.7862935Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) 2017-10-25T15:16:22.7862935Z ##[error]System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter 'Path' because it is null. 2017-10-25T15:16:22.7862935Z at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate) 2017-10-25T15:16:22.7862935Z at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext) 2017-10-25T15:16:22.7862935Z at System.Management.Automation.Interpreter.ActionCallInstruction6.Run(InterpretedFrame frame)
2017-10-25T15:16:22.7862935Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
2017-10-25T15:16:22.7862935Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
2017-10-25T15:16:22.7862935Z ##[error]System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter 'Message' because it is null.
2017-10-25T15:16:22.7862935Z at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
2017-10-25T15:16:22.7862935Z at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
2017-10-25T15:16:22.7862935Z at System.Management.Automation.Interpreter.ActionCallInstruction6.Run(InterpretedFrame frame) 2017-10-25T15:16:22.7862935Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) 2017-10-25T15:16:22.8331890Z ##[error]System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter 'Path' because it is null. 2017-10-25T15:16:22.8331890Z at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate) 2017-10-25T15:16:22.8331890Z at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext) 2017-10-25T15:16:22.8331890Z at System.Management.Automation.Interpreter.ActionCallInstruction6.Run(InterpretedFrame frame)
2017-10-25T15:16:22.8331890Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
2017-10-25T15:16:22.8331890Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
2017-10-25T15:16:22.8331890Z ##[error]System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter 'Path' because it is null.
2017-10-25T15:16:22.8331890Z at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
2017-10-25T15:16:22.8331890Z at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
2017-10-25T15:16:22.8331890Z at System.Management.Automation.Interpreter.ActionCallInstruction6.Run(InterpretedFrame frame) 2017-10-25T15:16:22.8331890Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) 2017-10-25T15:16:22.8331890Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) 2017-10-25T15:16:22.8488084Z ##[error]PowerShell script completed with 10 errors. 2017-10-25T15:16:22.8488084Z ##[section]Finishing: RunFromALM:

Hi,

We have configured an TFS agent according to the documentation, including the UFT service.

When we run it, in ALM a timeslot is created and the test will run fine.
When the test finishes, it will create a write error (see logging below) (not sure what it's trying to write)

In another thread we saw that not running it as a service solved it, but that is not the case with us.

We have tried:
-Running it as service or as command line
-Running it as administrator
-Making sure the files are 'unblocked' (is does not show that checkbox, but also removed it via powershell)
-gave owner right to the agent folders and UFTWorking folder
-removing work folder
-Reinstall agent
-rebooting TFS agent and uft agent/lab service agent

What should we do to make the WriteErrorException disappear?

Thanks in advance!

Logging:

2020-10-07T12:04:33.8689248Z ##[section]Starting: Run Smoketest on D4

2020-10-07T12:04:33.8845702Z ==============================================================================

2020-10-07T12:04:33.8845854Z Task : UFT ALM Lab Management

2020-10-07T12:04:33.8845957Z Description : Use this build step to run ALM server-side functional test sets and Build Verification Suites.

2020-10-07T12:04:33.8846052Z Version : 1.0.0

2020-10-07T12:04:33.8846155Z Author :

2020-10-07T12:04:33.8846223Z Help :

2020-10-07T12:04:33.8846299Z ==============================================================================

2020-10-07T12:04:33.9072306Z Preparing task execution handler.

2020-10-07T12:04:34.2254669Z Executing the powershell script: C:\Agent_work_tasks\AlmLabManagementTask_91001daf-aaaa-4444-a6ff-8acf9d222e3a\1.0.0\localTask.ps1

2020-10-07T12:04:53.5193872Z ALM Lab Management task recognized

2020-10-07T12:04:53.5194408Z

2020-10-07T12:04:53.5194534Z

2020-10-07T12:04:53.5201392Z Logged in successfully to ALM Server https://mfalm.Hostname.net/qcbin/ using UFTUser

2020-10-07T12:04:53.5201677Z

2020-10-07T12:04:53.5201875Z

2020-10-07T12:04:53.5203304Z Executing TEST_SET ID: 1701 in DOMAIN/PROJECT

2020-10-07T12:04:53.5203498Z

2020-10-07T12:04:53.5203608Z

2020-10-07T12:04:53.5204927Z Description: Smoketest - 401

2020-10-07T12:04:53.5205068Z

2020-10-07T12:04:53.5205174Z

2020-10-07T12:04:53.5206562Z TEST_SET run report for run id 1705 is at: https://mfalm.Hostname.net/qcbin/ui/?redirected&p= DOMAIN/PROJECT &execution-report#/test-set-report/1705

2020-10-07T12:04:53.5206733Z

2020-10-07T12:04:53.5206839Z

2020-10-07T12:04:53.5208124Z Polling... Run ID: 1705

2020-10-07T12:04:53.5208303Z

2020-10-07T12:04:53.5208409Z

2020-10-07T12:04:53.5209721Z Timeslot id: 1534

2020-10-07T12:04:53.5209858Z

2020-10-07T12:04:53.5210002Z

2020-10-07T12:04:53.5211253Z 2020-10-07 14:04:35:Timeslot ID '1534' was created successfully

2020-10-07T12:04:53.5211397Z

2020-10-07T12:04:53.5211546Z

2020-10-07T12:04:53.5212800Z 2020-10-07 14:04:36:Creating run-time data for run '1705' of 'Test Set' '1701' (Timeslot ID '1534'; BVS ID '2341')

2020-10-07T12:04:53.5213005Z

2020-10-07T12:04:53.5213112Z

2020-10-07T12:04:53.5214325Z 2020-10-07 14:04:36:TestSet ID: '1705' start time: '2020-10-07 14:04:36.687'

2020-10-07T12:04:53.5214526Z

2020-10-07T12:04:53.5214632Z

2020-10-07T12:04:53.5216039Z 2020-10-07 14:04:51:Timeslot ID '1534' was closed

2020-10-07T12:04:53.5216214Z

2020-10-07T12:04:53.5216320Z

2020-10-07T12:04:53.5217594Z Timeslot 1534 is Finished.

2020-10-07T12:04:53.5217795Z

2020-10-07T12:04:53.5217940Z

2020-10-07T12:04:53.5219133Z Timeslot start time: 2020-10-07 14:04:35, Timeslot end time: 2020-10-07 14:04:51

2020-10-07T12:04:53.5219282Z

2020-10-07T12:04:53.5219388Z

2020-10-07T12:04:53.5220631Z Run state of 1705: Finished, Completed successfully: Y

2020-10-07T12:04:53.5220779Z

2020-10-07T12:04:53.5220886Z

2020-10-07T12:04:53.5330587Z ##[error]Microsoft.PowerShell.Commands.WriteErrorException

2020-10-07T12:04:53.5567006Z ##[error]PowerShell script completed with 1 errors.

2020-10-07T12:04:53.5575145Z ##[section]Finishing: Run Smoketest on D4

Currently getting the following warning when executing from Azure Devops:

[warning]Task 'RunFromALM' (1.0.4) is using deprecated task execution handler. The task should use the supported task-lib: https://aka.ms/tasklib

Hi,
When I Queue my build to RunFromFileSystemTask (UFT) from TFS application, I obtain an error bellow:

Microsoft.PowerShell.Commands.WriteErrorException: Task Failed
PowerShell script completed with 1 errors.

Can You help me on this topic ?

Thanks.

Regards,
João Brito

We are using the UFT file system task to run the UFT functional tests during a TFS 2015 update 2 Release. According the manual we need to run the TFSAgent in interactive mode. This is not a stable solution because everytime the machine is rebooted or something else happens the agent is down. Is it possible to use the default Test Agent instead? This agent already has the possiblity to run interactive with a TFS Agent that runs as a service.

During execution of tasks in Azure DevOps (ADO) Pipeline using "UFT File System Execution" task with "Version : 1.0.9 " .. which is MicroFocus Add-In available in Azure Market Place to run Microfocus UFT automation scripts..

When Test Result is Error or Failed in the task log , ADO task is not showing as Error , instead it is showing as success ..

Version : 1.0,4 was correctly ..

see attached snapshot of error message using Version 1.0.9

Hey

Firstly thank you so much for this it has been a huge help getting some automated regression setup at my work working great for single tests

I have a question this note in the Wiki for Run Multiple tests from file system
"For multiple tests, the test path or test name should be separated by a comma."

I have tried this several different ways and can not get it to work every time it sends the request to the server it just includes it in one massive string .

e.g. I pass in C:\UFTTest\Test1,C:\UFTTest\Test2 and it does not split it via comma so I just get the following error File/Folder not found: 'C:\UFTTest\Test1,C:\UFTTest\Test2'

Thanks

I have integrated azure devops with uft but result i am not getting in Azure devops

My test cases is in my local system. I have given the path of my test cases in RUNFROMFILESYSTEM Plugin but i am getting error as "##[error]Could not find file 'C:\Shiva_work_tasks\RunFromFileSystemTask_cfbe1493-3bb1-44d5-ac87-7f14a148a6f2\1.0.4\task.json'.

Please help me on this or anyone encountered with this type of issues.

Trying to run ALM from On-Prem TFS, I don't see the report being attached to the TFS. And also getting lognet error.

The testsuite from ALM was Run and finished. A testreport was made in ALM.
The link to the report is written in the log.

2017-09-07T07:21:11.7888466Z ##[error]Microsoft.PowerShell.Commands.WriteErrorException
2017-09-07T07:21:12.0857188Z ##[error]PowerShell script completed with 1 errors.
2017-09-07T07:21:12.0857188Z ##[section]Finishing: AlmLabManagementTask

for complete log see attached file
UFT-plugin error.docx

When I try to run a build and execute UFT test cases after a successful build I get an error message telling me the \bin\PSModule.dll was not loaded because it could not find the module.

When I execute the build a second time I get much less information in the log files. All I get is:
Unable to load the task definition. I am at a complete loss. Please advise,
Thanks,
-Chris

Second run logs:

Starting: Build

Executing the following commandline:
C:\agent\agent\worker\vsoWorker.exe /name:Worker-3619c999-26bf-435d-a7ea-0af786469328 /id:3619c999-26bf-435d-a7ea-0af786469328 /rootFolder:"C:\agent" /logger:Forwarding,1.0.0;Verbosity=Verbose,Name=Agent5-2d9cf39e69c8196f5a996f7bdcee0abb;JobId=3619c999-26bf-435d-a7ea-0af786469328

Starting: Get sources

Syncing repository: Sample Application (TFVC)
Workspace Name: ws_3_3;Build\9f0b7312-06b2-462e-8c43-5870b1fc9ab2
tf get /version:16
Done syncing repository Sample Application to version 16 (workspace version C16)

Unable to load the task definition at C:\agent\tasks\RunFromALM\1.0.0\task.json
Worker Worker-3619c999-26bf-435d-a7ea-0af786469328 finished running job 3619c999-26bf-435d-a7ea-0af786469328

Finishing Build

First run logs:

2017-09-27T19:21:30.9101658Z Executing the powershell script: C:\agent\tasks\RunFromALM\1.0.0\localTask.ps1

2
2017-09-27T19:21:30.9492717Z ##[error]The specified module '\bin\PSModule.dll' was not loaded because no valid module file was found in any module directory.

3
2017-09-27T19:21:30.9663174Z ##[error]Cannot bind argument to parameter 'Path' because it is null.

4
2017-09-27T19:21:30.9683267Z ##[error]Cannot bind argument to parameter 'Path' because it is null.

5
2017-09-27T19:21:30.9693271Z ##[error]Cannot bind argument to parameter 'Path' because it is null.

6
2017-09-27T19:21:30.9713323Z ##[error]Cannot bind argument to parameter 'Path' because it is null.

7
2017-09-27T19:21:31.4024919Z ##[error]The term 'Invoke-RunFromAlmTask' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

8
2017-09-27T19:21:31.4034942Z ##[error]Cannot bind argument to parameter 'Path' because it is null.

9
2017-09-27T19:21:31.4055003Z ##[error]Cannot bind argument to parameter 'Message' because it is null.

10
2017-09-27T19:21:31.4285621Z ##[error]Cannot bind argument to parameter 'Path' because it is null.

11
2017-09-27T19:21:31.4295658Z ##[error]Cannot bind argument to parameter 'Path' because it is null.

Starting: Build

Executing the following commandline:
C:\agent\agent\worker\vsoWorker.exe /name:Worker-622e4112-0c55-4dcb-9457-efea73917600 /id:622e4112-0c55-4dcb-9457-efea73917600 /rootFolder:"C:\agent" /logger:Forwarding,1.0.0;Verbosity=Verbose,Name=Agent5-2d9cf39e69c8196f5a996f7bdcee0abb;JobId=622e4112-0c55-4dcb-9457-efea73917600

Starting: Get sources

Syncing repository: Sample Application (TFVC)
Workspace Name: ws_3_3;Build\9f0b7312-06b2-462e-8c43-5870b1fc9ab2
tf get /version:16
Done syncing repository Sample Application to version 16 (workspace version C16)

Unable to load the task definition at C:\agent\tasks\RunFromFileSystemTask\1.0.0\task.json
Worker Worker-622e4112-0c55-4dcb-9457-efea73917600 finished running job 622e4112-0c55-4dcb-9457-efea73917600

Finishing Build

@aslaakso - I see you are making changes here and in the MicroFocus repo. Does this mean a new version is going to get released soon? We're having some odd issues with the currently published version and a new release would be awesome!

Microsoft VSIX Installation Fails.

I am using hpe uft 14.0.1 and TFS 2017 on Windows 7 Ultimate. when i followed the tutorial for tfs and uft integration here, the vsix installer was not installing. I got this message in log file:
This extension is not installable on any currently installed products.

Please let me know if there is any other way to Integrate tfs and uft

thanks in advance.

2018-05-15T23:13:15.4401672Z ##[debug]Evaluating condition for step: 'RunFromFileSystemTask'
2018-05-15T23:13:15.4401672Z ##[debug]Evaluating: always()
2018-05-15T23:13:15.4401672Z ##[debug]Evaluating always:
2018-05-15T23:13:15.4401672Z ##[debug]=> (Boolean) True
2018-05-15T23:13:15.4401672Z ##[debug]Expanded: True
2018-05-15T23:13:15.4401672Z ##[debug]Result: True
2018-05-15T23:13:15.4401672Z ##[section]Starting: RunFromFileSystemTask
2018-05-15T23:13:15.4713685Z ==============================================================================
2018-05-15T23:13:15.4713685Z Task : UFT File System Execution
2018-05-15T23:13:15.4713685Z Description : Execute UFT tests from file system
2018-05-15T23:13:15.4713685Z Version : 1.0.0
2018-05-15T23:13:15.4713685Z Author :
2018-05-15T23:13:15.4713685Z Help :
2018-05-15T23:13:15.4713685Z ==============================================================================
2018-05-15T23:13:15.5181872Z Preparing task execution handler.
2018-05-15T23:13:20.4253855Z Executing the powershell script: C:\tfs\vsts-agent-win7-x64-2.122.2_work_tasks\RunFromFileSystemTask_cfbe1493-3bb1-44d5-ac87-7f14a148a6f0\1.0.0\localTask.ps1
2018-05-15T23:13:20.4253855Z ##[debug]PowerShellHandler.Execute - AddCommand(C:\tfs\vsts-agent-win7-x64-2.122.2_work_tasks\RunFromFileSystemTask_cfbe1493-3bb1-44d5-ac87-7f14a148a6f0\1.0.0\localTask.ps1)
2018-05-15T23:13:20.4253855Z ##[debug]PowerShellHandler.Execute - Add inputParameters
2018-05-15T23:13:20.4253855Z ##[debug]PowerShellHandler.Execute - AddParameter(testPathInput=C:\Users\shri\Desktop\New folder\TestTFS.mtb)
2018-05-15T23:13:20.4253855Z ##[debug]PowerShellHandler.Execute - AddParameter(timeOutIn=)
2018-05-15T23:13:20.8779749Z ##[debug]PowerShellHandler.Execute - Invoke
2018-05-15T23:13:21.1588925Z ##[debug]Loading module from path 'C:\tfs\UFTWorking\bin\PSModule.dll'.
2018-05-15T23:13:21.2369246Z ##[debug]Importing cmdlet 'Invoke-RunFromAlmTask'.
2018-05-15T23:13:21.2369246Z ##[debug]Importing cmdlet 'Invoke-FSTask'.
2018-05-15T23:13:21.2525308Z ##[debug]Launcher C:\tfs\UFTWorking\HpToolsLauncher.exe
2018-05-15T23:13:21.2525308Z ##[debug]Aborter** C:\tfs\UFTWorking\HpToolsAborter.exe
2018-05-15T23:13:21.2681371Z ##[debug]Properties saved in : C:\tfs\UFTWorking\props\props15052018191321SSS.txt
2018-05-15T23:13:21.2681371Z ##[debug]runType : FileSystem
2018-05-15T23:13:21.2681371Z ##[debug]PerScenarioTimeOut : -1
2018-05-15T23:13:21.2837446Z ##[debug]Test1 : C:\Users\shri\Desktop\New folder\TestTFS.mtb
2018-05-15T23:13:21.2837446Z ##[debug]resultsFilename : C:\tfs\UFTWorking\res\Results15052018191321SSS.xml
2018-05-15T23:13:23.7183610Z "Started..."
2018-05-15T23:13:23.7807864Z Launcher timeout is 10675199::02:48:05
2018-05-15T23:13:23.7807864Z Controller Polling Interval: 30 seconds
2018-05-15T23:13:23.7807864Z PerScenarioTimeout: 10675199::02:48:05 minutes
2018-05-15T23:13:23.7807864Z FileSystemTestRunner timeout is 10675199.02:48:05.4775807
2018-05-15T23:13:23.7807864Z Mc connection info is - Mc HostAddress: , McPort: 8080, Username: , UseSSL: 0, UseProxy: 0, ProxyType: 0, ProxyAddress: , ProxyPort: 0, ProxyAuth: 0, ProxyUser:
2018-05-15T23:13:23.7807864Z 2 tests found:
2018-05-15T23:13:23.7807864Z C:\Users\shri\Desktop\New folder\GUITest1
2018-05-15T23:13:23.7807864Z C:\Users\shri\Desktop\New folder\URL
2018-05-15T23:13:23.7807864Z ============================================================================
2018-05-15T23:13:24.2489820Z 15/05/2018 19:13:24 Running: C:\Users\shri\Desktop\New folder\GUITest1
2018-05-15T23:13:24.2645887Z Test result: Error
2018-05-15T23:13:24.2645887Z 15/05/2018 19:13:24 Test complete: C:\Users\shri\Desktop\New folder\GUITest1
2018-05-15T23:13:24.2645887Z -------------------------------------------------------------------------------------------------------
2018-05-15T23:13:24.2645887Z 15/05/2018 19:13:24 Running: C:\Users\shri\Desktop\New folder\URL
2018-05-15T23:13:24.2801945Z Test result: Error
2018-05-15T23:13:24.2801945Z 15/05/2018 19:13:24 Test complete: C:\Users\shri\Desktop\New folder\URL
2018-05-15T23:13:24.2801945Z -------------------------------------------------------------------------------------------------------
2018-05-15T23:13:43.8225944Z ================================================
2018-05-15T23:13:43.8225944Z Run status: Job failed, total tests: 2, succeeded: 0, failures: 0, errors: 2
2018-05-15T23:13:43.8225944Z Error : C:\Users\shri\Desktop\New folder\GUITest1
2018-05-15T23:13:43.8225944Z Error : C:\Users\shri\Desktop\New folder\URL
2018-05-15T23:13:43.8225944Z ================================================
2018-05-15T23:13:43.8537877Z ##[debug]Return code: -1
2018-05-15T23:13:43.8537877Z ##[debug]Remove temp files
2018-05-15T23:13:43.8537877Z ##[debug]C:\tfs\UFTWorking\res*.xml
2018-05-15T23:13:43.8850015Z ##[debug]Remove temp files complited
2018-05-15T23:13:43.9318220Z ##[error]Microsoft.PowerShell.Commands.WriteErrorException: Task Failed
2018-05-15T23:13:43.9318220Z ##[debug]Processed: ##vso[task.logissue type=error;]Microsoft.PowerShell.Commands.WriteErrorException: Task Failed
2018-05-15T23:13:43.9942466Z ##[error]PowerShell script completed with 1 errors.
2018-05-15T23:13:43.9942466Z ##[section]Finishing: RunFromFileSystemTask

The installtion expects UFT to be installed on the TFS agent machine, even when I only wish to run tests remotely on a separate remote testing host (never locally from ALM or from the FileSystem). Why is UFT needed for this?

In "RunFromALM" build step, the below error is displaying continuously.

2019-01-16T07:47:31.9549824Z ##[section]Starting: RunFromALM:
2019-01-16T07:47:31.9553421Z ==============================================================================
2019-01-16T07:47:31.9553500Z Task : UFT ALM Execution
2019-01-16T07:47:31.9553554Z Description : Execute UFT tests from ALM
2019-01-16T07:47:31.9553625Z Version : 1.0.0
2019-01-16T07:47:31.9553674Z Author :
2019-01-16T07:47:31.9553721Z Help :
2019-01-16T07:47:31.9553792Z ==============================================================================
2019-01-16T07:47:31.9684816Z Preparing task execution handler.
2019-01-16T07:47:47.2628062Z Executing the powershell script: D:\a_tasks\RunFromALM_a571ae7c-e100-42e1-8ced-498b46029770\1.0.0\localTask.ps1
2019-01-16T07:47:48.0405346Z ##[error]System.IO.FileNotFoundException: The specified module '\bin\PSModule.dll' was not loaded because no valid module file was found in any module directory.
2019-01-16T07:47:48.1774166Z ##[error]System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter 'Path' because it is null.
2019-01-16T07:47:48.1774525Z at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
2019-01-16T07:47:48.1774646Z at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
2019-01-16T07:47:48.1774734Z at System.Management.Automation.Interpreter.ActionCallInstruction6.Run(InterpretedFrame frame) 2019-01-16T07:47:48.1774842Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) 2019-01-16T07:47:48.1774924Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) 2019-01-16T07:47:48.1788346Z ##[error]System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter 'Path' because it is null. 2019-01-16T07:47:48.1788615Z at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate) 2019-01-16T07:47:48.1788730Z at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext) 2019-01-16T07:47:48.1788816Z at System.Management.Automation.Interpreter.ActionCallInstruction6.Run(InterpretedFrame frame)
2019-01-16T07:47:48.1788919Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
2019-01-16T07:47:48.1788993Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
2019-01-16T07:47:48.1795881Z ##[error]System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter 'Path' because it is null.
2019-01-16T07:47:48.1796133Z at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
2019-01-16T07:47:48.1796249Z at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
2019-01-16T07:47:48.1796333Z at System.Management.Automation.Interpreter.ActionCallInstruction6.Run(InterpretedFrame frame) 2019-01-16T07:47:48.1796434Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) 2019-01-16T07:47:48.1796512Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) 2019-01-16T07:47:48.1802096Z ##[error]System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter 'Path' because it is null. 2019-01-16T07:47:48.1803484Z at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate) 2019-01-16T07:47:48.1803602Z at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext) 2019-01-16T07:47:48.1803686Z at System.Management.Automation.Interpreter.ActionCallInstruction6.Run(InterpretedFrame frame)
2019-01-16T07:47:48.1804146Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
2019-01-16T07:47:48.1804228Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
2019-01-16T07:47:59.1485766Z ##[error]System.Management.Automation.CommandNotFoundException: The term 'Invoke-RunFromAlmTask' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2019-01-16T07:47:59.1486164Z at System.Management.Automation.CommandDiscovery.LookupCommandInfo(String commandName, CommandTypes commandTypes, SearchResolutionOptions searchResolutionOptions, CommandOrigin commandOrigin, ExecutionContext context)
2019-01-16T07:47:59.1486277Z at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String commandName, CommandOrigin commandOrigin, Nullable1 useLocalScope) 2019-01-16T07:47:59.1486369Z at System.Management.Automation.ExecutionContext.CreateCommand(String command, Boolean dotSource) 2019-01-16T07:47:59.1486458Z at System.Management.Automation.PipelineOps.AddCommand(PipelineProcessor pipe, CommandParameterInternal[] commandElements, CommandBaseAst commandBaseAst, CommandRedirection[] redirections, ExecutionContext context) 2019-01-16T07:47:59.1486587Z at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext) 2019-01-16T07:47:59.1486670Z at System.Management.Automation.Interpreter.ActionCallInstruction6.Run(InterpretedFrame frame)
2019-01-16T07:47:59.1486761Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
2019-01-16T07:47:59.1506004Z ##[error]System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter 'Path' because it is null.
2019-01-16T07:47:59.1506314Z at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
2019-01-16T07:47:59.1506416Z at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
2019-01-16T07:47:59.1506529Z at System.Management.Automation.Interpreter.ActionCallInstruction6.Run(InterpretedFrame frame) 2019-01-16T07:47:59.1506604Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) 2019-01-16T07:47:59.1506695Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) 2019-01-16T07:47:59.1510607Z ##[error]System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter 'Message' because it is null. 2019-01-16T07:47:59.1510871Z at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate) 2019-01-16T07:47:59.1510970Z at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext) 2019-01-16T07:47:59.1511578Z at System.Management.Automation.Interpreter.ActionCallInstruction6.Run(InterpretedFrame frame)
2019-01-16T07:47:59.1511653Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
2019-01-16T07:47:59.1689689Z ##[error]System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter 'Path' because it is null.
2019-01-16T07:47:59.1689979Z at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
2019-01-16T07:47:59.1690294Z at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
2019-01-16T07:47:59.1690420Z at System.Management.Automation.Interpreter.ActionCallInstruction6.Run(InterpretedFrame frame) 2019-01-16T07:47:59.1690497Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) 2019-01-16T07:47:59.1690591Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) 2019-01-16T07:47:59.1693621Z ##[error]System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter 'Path' because it is null. 2019-01-16T07:47:59.1693884Z at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate) 2019-01-16T07:47:59.1694015Z at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext) 2019-01-16T07:47:59.1694107Z at System.Management.Automation.Interpreter.ActionCallInstruction6.Run(InterpretedFrame frame)
2019-01-16T07:47:59.1694197Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
2019-01-16T07:47:59.1694272Z at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
2019-01-16T07:47:59.2726426Z ##[error]PowerShell script completed with 10 errors.
2019-01-16T07:47:59.2733994Z ##[section]Finishing: RunFromALM:

Hi,

I am getting below error while trying to run unpack.ps1 -

PS C:\UFT-Azure> C:\UFT-Azure\unpack.ps1
At C:\UFT-Azure\unpack.ps1:168 char:21

•             Sign up
  

•                 ~
  

The ampersand (&) character is not allowed. The & op
quotation marks ("&") to pass it as part of a string
At C:\UFT-Azure\unpack.ps1:195 char:190

• ... ata-ga-click="(Logged out) Header, go to Featu

The '<' operator is reserved for future use.
At C:\UFT-Azure\unpack.ps1:195 char:261

• ... ="Bump-link-symbol float-right text-normal tex

The ampersand (&) character is not allowed. The & op
quotation marks ("&") to pass it as part of a string
At C:\UFT-Azure\unpack.ps1:209 char:255

• ... ogged out) Header, go to Customer stories">Cus

The '<' operator is reserved for future use.
At C:\UFT-Azure\unpack.ps1:209 char:326

• ... ="Bump-link-symbol float-right text-normal tex

The ampersand (&) character is not allowed. The & op
quotation marks ("&") to pass it as part of a string
At C:\UFT-Azure\unpack.ps1:210 char:231

• ... ata-ga-click="(Logged out) Header, go to Secur

The '<' operator is reserved for future use.
At C:\UFT-Azure\unpack.ps1:210 char:302

• ... ="Bump-link-symbol float-right text-normal tex

The ampersand (&) character is not allowed. The & op
quotation marks ("&") to pass it as part of a string
At C:\UFT-Azure\unpack.ps1:233 char:222

• ... a-click="(Logged out) Header, go to Explore">E

The '<' operator is reserved for future use.
At C:\UFT-Azure\unpack.ps1:233 char:293

• ... ="Bump-link-symbol float-right text-normal tex

The ampersand (&) character is not allowed. The & op
quotation marks ("&") to pass it as part of a string
At C:\UFT-Azure\unpack.ps1:236 char:107

• ... text-normal text-mono f5 mb-2 border-lg-top p

The ampersand (&) character is not allowed. The & op
quotation marks ("&") to pass it as part of a string
Not all parse errors were reported. Correct the rep
+ CategoryInfo : ParserError: (:) [], P
+ FullyQualifiedErrorId : AmpersandNotAllowed

Trying to run tests using the RunFromALM plugin. I eventually get the output below. I have logged in as the build user and installed TDConnectivity as suggested by the error message.

I've also opened up the specified directory permissions to everyone all rights.

Help is greatly appreciated.

2017-10-27T15:38:13.5356641Z ##[section]Starting: RunFromALM: 2017-10-27T15:38:13.5512861Z ============================================================================== 2017-10-27T15:38:13.5512861Z Task : UFT ALM Execution 2017-10-27T15:38:13.5512861Z Description : Execute UFT tests from ALM 2017-10-27T15:38:13.5512861Z Version : 1.0.0 2017-10-27T15:38:13.5512861Z Author : 2017-10-27T15:38:13.5512861Z Help : 2017-10-27T15:38:13.5512861Z ============================================================================== 2017-10-27T15:38:13.5825398Z Preparing task execution handler. 2017-10-27T15:38:14.3950497Z Executing the powershell script: E:\devagent\Agent1\_work\_tasks\RunFromALM_a571ae7c-e100-42e1-8ced-498b46029770\1.0.0\localTask.ps1 2017-10-27T15:38:14.3950497Z "Started..." 2017-10-27T15:38:14.3950497Z Timeout is set to: -1 2017-10-27T15:38:14.3950497Z Run mode is set to: RUN_LOCAL 2017-10-27T15:38:15.9575798Z ============================================================================ 2017-10-27T15:38:15.9575798Z Starting test set execution 2017-10-27T15:38:15.9732010Z Test set name: CI_Test_Set_for_Dascalos, Test set id: 803 2017-10-27T15:39:16.1081720Z Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://daycrtqc04:8080/qcbin/TDConnectivity_index.html 2017-10-27T15:39:17.4050579Z ##[error]System.IO.FileNotFoundException: Could not find file 'C:\admtfs\UFTWorking\res\Results27102017113813SSS.xml'. 2017-10-27T15:39:17.4050579Z File name: 'C:\admtfs\UFTWorking\res\Results27102017113813SSS.xml' 2017-10-27T15:39:17.4050579Z at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) 2017-10-27T15:39:17.4050579Z at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) 2017-10-27T15:39:17.4050579Z at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) 2017-10-27T15:39:17.4050579Z at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean checkHost) 2017-10-27T15:39:17.4050579Z at System.IO.File.InternalReadAllText(String path, Encoding encoding, Boolean checkHost) 2017-10-27T15:39:17.4050579Z at PSModule.AbstractLauncherTaskCmdlet.CollateResults(String resultFile, String log, String resdir) 2017-10-27T15:39:17.4050579Z at PSModule.AbstractLauncherTaskCmdlet.ProcessRecord() 2017-10-27T15:39:17.4206802Z ##[error]PowerShell script completed with 1 errors. 2017-10-27T15:39:17.4206802Z ##[section]Finishing: RunFromALM:

13:24.2645887Z -------------------------------------------------------------------------------------------------------

2018-05-15T23:13:15.4401672Z ##[debug]Evaluating condition for step: 'RunFromFileSystemTask'
2018-05-15T23:13:15.4401672Z ##[debug]Evaluating: always()
2018-05-15T23:13:15.4401672Z ##[debug]Evaluating always:
2018-05-15T23:13:15.4401672Z ##[debug]=> (Boolean) True
2018-05-15T23:13:15.4401672Z ##[debug]Expanded: True
2018-05-15T23:13:15.4401672Z ##[debug]Result: True
2018-05-15T23:13:15.4401672Z ##[section]Starting: RunFromFileSystemTask
2018-05-15T23:13:15.4713685Z ==============================================================================
2018-05-15T23:13:15.4713685Z Task : UFT File System Execution
2018-05-15T23:13:15.4713685Z Description : Execute UFT tests from file system
2018-05-15T23:13:15.4713685Z Version : 1.0.0
2018-05-15T23:13:15.4713685Z Author :
2018-05-15T23:13:15.4713685Z Help :
2018-05-15T23:13:15.4713685Z ==============================================================================
2018-05-15T23:13:15.5181872Z Preparing task execution handler.
2018-05-15T23:13:20.4253855Z Executing the powershell script: C:\tfs\vsts-agent-win7-x64-2.122.2_work_tasks\RunFromFileSystemTask_cfbe1493-3bb1-44d5-ac87-7f14a148a6f0\1.0.0\localTask.ps1
2018-05-15T23:13:20.4253855Z ##[debug]PowerShellHandler.Execute - AddCommand(C:\tfs\vsts-agent-win7-x64-2.122.2_work_tasks\RunFromFileSystemTask_cfbe1493-3bb1-44d5-ac87-7f14a148a6f0\1.0.0\localTask.ps1)
2018-05-15T23:13:20.4253855Z ##[debug]PowerShellHandler.Execute - Add inputParameters
2018-05-15T23:13:20.4253855Z ##[debug]PowerShellHandler.Execute - AddParameter(testPathInput=C:\Users\shri\Desktop\New folder\TestTFS.mtb)
2018-05-15T23:13:20.4253855Z ##[debug]PowerShellHandler.Execute - AddParameter(timeOutIn=)
2018-05-15T23:13:20.8779749Z ##[debug]PowerShellHandler.Execute - Invoke
2018-05-15T23:13:21.1588925Z ##[debug]Loading module from path 'C:\tfs\UFTWorking\bin\PSModule.dll'.
2018-05-15T23:13:21.2369246Z ##[debug]Importing cmdlet 'Invoke-RunFromAlmTask'.
2018-05-15T23:13:21.2369246Z ##[debug]Importing cmdlet 'Invoke-FSTask'.
2018-05-15T23:13:21.2525308Z ##[debug]Launcher C:\tfs\UFTWorking\HpToolsLauncher.exe
2018-05-15T23:13:21.2525308Z ##[debug]Aborter** C:\tfs\UFTWorking\HpToolsAborter.exe
2018-05-15T23:13:21.2681371Z ##[debug]Properties saved in : C:\tfs\UFTWorking\props\props15052018191321SSS.txt
2018-05-15T23:13:21.2681371Z ##[debug]runType : FileSystem
2018-05-15T23:13:21.2681371Z ##[debug]PerScenarioTimeOut : -1
2018-05-15T23:13:21.2837446Z ##[debug]Test1 : C:\Users\shri\Desktop\New folder\TestTFS.mtb
2018-05-15T23:13:21.2837446Z ##[debug]resultsFilename : C:\tfs\UFTWorking\res\Results15052018191321SSS.xml
2018-05-15T23:13:23.7183610Z "Started..."
2018-05-15T23:13:23.7807864Z Launcher timeout is 10675199::02:48:05
2018-05-15T23:13:23.7807864Z Controller Polling Interval: 30 seconds
2018-05-15T23:13:23.7807864Z PerScenarioTimeout: 10675199::02:48:05 minutes
2018-05-15T23:13:23.7807864Z FileSystemTestRunner timeout is 10675199.02:48:05.4775807
2018-05-15T23:13:23.7807864Z Mc connection info is - Mc HostAddress: , McPort: 8080, Username: , UseSSL: 0, UseProxy: 0, ProxyType: 0, ProxyAddress: , ProxyPort: 0, ProxyAuth: 0, ProxyUser:
2018-05-15T23:13:23.7807864Z 2 tests found:
2018-05-15T23:13:23.7807864Z C:\Users\shri\Desktop\New folder\GUITest1
2018-05-15T23:13:23.7807864Z C:\Users\shri\Desktop\New folder\URL
2018-05-15T23:13:23.7807864Z ============================================================================
2018-05-15T23:13:24.2489820Z 15/05/2018 19:13:24 Running: C:\Users\shri\Desktop\New folder\GUITest1
2018-05-15T23:13:24.2645887Z Test result: Error
2018-05-15T23:13:24.2645887Z 15/05/2018 19:13:24 Test complete: C:\Users\shri\Desktop\New folder\GUITest1
2018-05-15T23:13:24.2645887Z -------------------------------------------------------------------------------------------------------
2018-05-15T23:13:24.2645887Z 15/05/2018 19:13:24 Running: C:\Users\shri\Desktop\New folder\URL
2018-05-15T23:13:24.2801945Z Test result: Error
2018-05-15T23:13:24.2801945Z 15/05/2018 19:13:24 Test complete: C:\Users\shri\Desktop\New folder\URL
2018-05-15T23:13:24.2801945Z -------------------------------------------------------------------------------------------------------
2018-05-15T23:13:43.8225944Z ================================================
2018-05-15T23:13:43.8225944Z Run status: Job failed, total tests: 2, succeeded: 0, failures: 0, errors: 2
2018-05-15T23:13:43.8225944Z Error : C:\Users\shri\Desktop\New folder\GUITest1
2018-05-15T23:13:43.8225944Z Error : C:\Users\shri\Desktop\New folder\URL
2018-05-15T23:13:43.8225944Z ================================================
2018-05-15T23:13:43.8537877Z ##[debug]Return code: -1
2018-05-15T23:13:43.8537877Z ##[debug]Remove temp files
2018-05-15T23:13:43.8537877Z ##[debug]C:\tfs\UFTWorking\res*.xml
2018-05-15T23:13:43.8850015Z ##[debug]Remove temp files complited
2018-05-15T23:13:43.9318220Z ##[error]Microsoft.PowerShell.Commands.WriteErrorException: Task Failed
2018-05-15T23:13:43.9318220Z ##[debug]Processed: ##vso[task.logissue type=error;]Microsoft.PowerShell.Commands.WriteErrorException: Task Failed
2018-05-15T23:13:43.9942466Z ##[error]PowerShell script completed with 1 errors.
2018-05-15T23:13:43.9942466Z ##[section]Finishing: RunFromFileSystemTask

You forgot to package hpe.application.automation.tfs.almrestrunner-1.0-jar-with-dependencies.jar in the zip file.

Unable to access jarfile C:\xxxx\hpe.application.automation.tfs.almrestrunner-1.0-jar-with-dependencies.jar

If you are wanting to run tests from ALM - does it matter which version of UFT is installed on the execution machines? We have UFT version 12.52 installed on the remote machines and I'm hoping we can make this extension work.

I'm making an assumption here that the requirement of version UFT 14.0.1 is a requirement for the tests to be run on the local TFS machine. Can you please confirm?

I have provided around 20 Testscripts in mtb file, It executes only the first 8 testscripts and skips rest of them. It is getting struck after executing 8 scripts

Can this be configured to support test output parameters? Then pass them as input to the next test?