SoapUI Pro for Azure DevOps - Tests passing, task failing.

[KevinRead]

I've got the SoapUI Pro for Azure DevOps task running in a pipeline successfully.

From the logs I can see that all the tests are passing, but the task fails with the following error:

Cannot validate argument on parameter 'ArgumentList'.

I'm using version 2.* of the task, the the only field configured is the Path to SoapUI Pro project.

Extract from the end of the log:

2019-08-07T04:23:29.4304120Z 14:23:26,609 INFO [SoapUIProTestCaseRunner] Project [xx.api] finished with status [PASS] in 33034ms
2019-08-07T04:23:29.4305069Z
2019-08-07T04:23:29.4305219Z 14:23:27,543 INFO [SoapUIProTestCaseRunner] Created report at file:/C:/Program%20Files/SmartBear/ReadyAPI-2.8.0/bin/index.html
2019-08-07T04:23:29.4305376Z 14:23:27,545 INFO [license] ReadyAPI 2.8.0 shutting down
2019-08-07T04:23:29.4305443Z
2019-08-07T04:23:29.8447648Z ##[error]Cannot validate argument on parameter 'ArgumentList'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.
2019-08-07T04:23:31.6850957Z ##[section]Finishing: SoapUI Pro for Azure DevOps

[Olga_T]

Thanks for reaching out, @KevinRead.

Community, has anyone faced a similar situation? 

[KevinRead · Accepted solution]

An update.

After setting the system.debug variable to true in my release definition, I was able trace through the error stack and into the SoapUIProFunctionalTestingTask.ps1 script.  

I deduced that the Common.TestResultsDirectory variable had not been set.  No where in the documentation does it mention this needs to be done.

So after adding the Common.TestResultsDirectory variable to the release, results were published to it and the task is now passing.

[Olga_T]

It's great to hear you have managed to solve this!

And thank you for sharing the solution!

[pravekdadhwal]

Dear KevinRead,

I am having similar issue what you were facing.

##[error]Cannot validate argument on parameter 'ArgumentList'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.

I know you provided the solution also, but I have just started working on SOAPUI and really new to understand what you said. In my Release definition, I have added Common.TestResultsDirectory variable, but not sure the 'Value' that I should mention here.

I am running my SOAP tests through release pipeline and the VSTS Agent is sitting on another machine. The tests are running fine but the problem is, its not publishing the results and failing with the above error.

Would you be able to provide more information on what exactly you did around Common.TestResultsDirectory variable??

Thanks in anticipation!

Regards,

Pravek Dadhwal

[KevinRead · Accepted solution]

Pravek,

Give up on using it in a Release pipeline.  Switch to a Build pipeline and the Common.TestResultsDirectory variable will be set for you.

[Nastya_Khovrina]

Hi Pravek,

You can read more about the "Common.TestResultsDirectory" variable here: https://docs.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&tabs=yaml#...