Execution plan looks like below. From which I am trying to run Menu5_US and its child test items. But the other groups also getting executed. Until yesterday only the specified group in the testFiltercriteria was getting executed in azure pipeline.
Originally posted by NikhileshJ on February 18, 2025
We are also facing the same issue; The issue seems be due the Test Adapter update TestComplete test adapter - Visual Studio Marketplace. For the time being reverting to old version of Test Adapter worked. Have also created ticket Case #00694491
Originally posted by dhundley on February 18, 2025
i am seeing something similar. Starting yesterday, the completion status (Passed or Failed) are not appearing in the azure devops results log as the pipeline runs. I’ve also noticed that, in a pipeline that has multiple steps and each step is set up to run on a different VM that it is ignoring the Agent.Name equals in the Demands section and is running on a VM where it’s not supposed to causing it to use the wrong sets of login credentials for that test. I am having to disable all my pipelines until this is resolved. Can the version of the TestComplete test adapter that was released yesterday be rolled back to the prior release temporarily to see if that alleviates the issue?
Originally posted by NikhileshJ on February 18, 2025
Unfortunately, I do not see any option to cherry pick adapter version. It by default installs the faulty one. If you have some pipeline which have not been run with latest adapter, you can copy the old adapter folder from the work directory/s of that pipeline and use it. You will have to-
Provide the hardcoded path of the adapter.
In case you’re passing some command line parameters, then you will have to write some script to update Adapter options.json file as per your need.
Originally posted by bhapriravi on February 18, 2025
We are also badly impacted.
We use the following filters for tests from ADO based on the test selector: test plan. We provide Test Plan and Test Suite IDs to actually run the tests, as shown below. This stopped working since yesterday.
Originally posted by simonaferrara on February 19, 2025
I’ve got the same issue, from yesterday 17/2 in the morning.
The testFiltercriteria property of VSTest task seems not handled anymore; the tests are executed from the project’s first test item, without filtering by using this property.
Please quickly help to resolve the issue, since it highly impact our automatic tests execution.
Originally posted by Chandrika_nag1 on February 19, 2025
Hi NikhileshJ , How are you hardcoding the older version? I am using ADO pipeline tasks where for this I am using “TestComplete test adapter installer” task, with this task how can i use older version of test adapter?
If you have old version copy those TestAdapter files (it should be in Work folder of the devops agent) on C drive and in VSTest path to custom updaters can be the path. Below is the working example:
Originally posted by NikhileshJ on February 19, 2025
If you have the old version with you(if you’re lucky you can find it in old pipeline src folder), If you’re using VSTest@2 task, you can hard code it here
-task: VSTest@2
displayName: ‘Start TestExecute runner’
inputs:
testAssemblyVer2: ‘project.pjs’
testFiltercriteria: ‘Project=Test&Group~“to_research”’
vsTestVersion: toolsInstaller
pathtoCustomTestAdapters: Test AdapterPath(you need to copy the old version here)
publishRunAttachments: false
preferredExecutor: TE
I understand it is very specific fix and will work only if you somehow manage to have old Adapter version, still putting it out here if someone benefits from it.