Solved
testFiltercriteria not applied
Until yesterday test was running fine with the below highlighted test criteria in azure pipeline. After Updating the test agent test are not getting filtered from the execution plan. Exec...
Forum Discussion
I've found a working workaround, by using the previous older TestAdapter version 1.15069.139, till the fix will be available.
I share it with you since this could temporarily resolve the issue also for you and let it possible to not block your test automation execution.
You can specify it as follows within your release pipeline, writing the complete working version on the task after InstallTestCompleteAdapter:
- task: InstallTestCompleteAdapter@1.15069.139
displayName: "TestComplete test adapter installer"
continueOnError: false
inputs:
installExecutor: false
updateExecutor: false
With this configuration, next VSTest tasks will work as expected.
Surely, when SmartBear or Microsoft will provide the fix, this workaround will need to be reverted to get the latest TestAdapter version.
Can you tell if we can do something like in azure classic pipelines
right after i posted my last message about the zoom call i had with the smartbear tech guy, he replied with a workaround solution for me and my azure classic pipelines. i've already implemented it on a couple of my VM's and verified that it does work. it is a way to use the previous, stable, working version of the test adapter which is in the zip file of the link below. hope this works for all of you. here is his email to me. Let me know if you have any questions.
Developers have reproduced and have been working on the issue. They will try to set up and implement a potential roll back strategy if there solutions don't work. Should have an update on Monday.
In the meantime, I actually had luck with successful pipelines using the following test adapter below:
It's the old one so it works fine. Do the following same steps again, but with this test adapter and see if you still have issues:
* Extract the zipped folder (may need to extract it in your desktop)
* the three dlls you need will be under "InstallTestCompleteAdapterTask\Modules"
* In your pipeline, disable the "TestComplete test adapter" step.
* In your VSTest step, look for "Path to custom test adapter" text field
* Copy the full path of the "InstallTestCompleteAdapterTask\Modules" to the textfield
one caveat that my tech guy just informed me of
- Test items in the execution plan will run. Won't be able to run tags or project items.
i don't use tags so this does not affect me but wanted to pass it along just in case others do.
one thing i have discovered with this workaround is that it does not appear to be producing results logs that i can view. i'm waiting for a response from my tech guy about that.
I tried the following it is working and able to see logs also
go to the following directory: C:\Program Files (x86)\SmartBear\TestComplete 15\TFS Integration
Change the extension of the file "smartbearsoftware.install-testcomplete-adapter-task-for-tfs-15.72.60" to a zip file
Extract the zipped folder (may need to extract it in your desktop)
the three dlls you need will be under "InstallTestCompleteAdapterTask\Modules"* In your pipeline, disable the "TestComplete test adapter" step.
In your VSTest step, look for "Path to custom test adapter" text field
Copy the full path of the "InstallTestCompleteAdapterTask\Modules" to the textfield
I'm sorry but I'm using yml release pipelines, so I cannot find a solution for your classic pipelines. Please search on how to configure a specific version within the classic task, as can be done within yml ones.
