We are building a new experience for our SmartBear Community.
This site is now read-only. You can still browse and search as usual. Learn More
This site is now read-only. You can still browse and search as usual. Learn More
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.
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.
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.
It's great to hear you have managed to solve this!
And thank you for sharing the solution!