Forum Discussion
As a result of opening a case about this with Smartbear, I had a zoom call with one of their techs late yesterday afternoon. He recorded our session as I showed him an example of one of our pipelines that is no longer working as expected since the release of the new TestComplete test adapter. I first showed him how the execution plan in the TestComplete project suite has the three groups in the project and then showed the step in our pipeline that has the Group~<third group name> which is supposed to only run the test cases in that specific group. After starting the pipeline I showed him on the VM where it runs that it was ignoring the Group~<third group name> filter and was running the first test case from the first group name listed in the execution plan.
He tried to recreate the problem as he shared his screen with me but was unable to reproduce this issue on his end. Nevertheless, he saw it on my side and will be updating me with any developments. Unfortunately, the folks who are apparently going to be the ones working on this are in Europe so it clearly won't be until sometime today or early next week before I hear anything back. I did suggest that Smartbear should rollback to the previously stable, working release of the test adapter but I have not gotten a reply to that suggestion so far. If I hear anything I will be sure to post it to this group chat.