ContributionsMost RecentMost LikesSolutionsRe: Execution plan. Enable Disable redesign Yes, you are right. There are two columns with checkboxes. But I set the value in the column "test case" once and never changed it. At the same time, occasionally, I have to run a group of tests in the middle of the playlist. Also, the context menus are different even though they have the same order of items. One has icons another - do not. Execution plan. Enable Disable redesign Execution plan. Enabled/disabled The most often scenario for us: Run tests with only several items enabled. Items can be in different groups 1. The Context menu is complicated Every time I have to search for the proper option, when I expect it to be in the first, or second position Also often after disabling the part of the playlist I accidentally press 'Enable All' instead of 'Enable selected' and then I have to start from scratch because Ctrl+Z also does not work on this tab Just 'Enable' and 'Disable' menu items will be enough (maybe 'toggle' may stay, someone can use it) BUT enable or disable action should apply for all selected items So 'Enable all' action could be performed by pressing Ctrl+A and then ClickR, 'Enable\Disable|Enable' Same for 'Disable all' 2. Enabling the item does not enable the parent items So you have to click each parent manually. 3. Ctrl+Z should work in case of undo Enbled Disabled DevExpress htmlContentControl TilesView Recently we started using DevExpress controls on our project. Mapping them is an unobvious task. Object Spy can't give me the required result. I've tried recording tests and it helped me in previous cases but not with the last. We have two types of panels shown below: Recording the tests gives me htmlContentControl.Click(107, 23); This approach obviously seems wrong to me. Because I want to click a text, not just a point of a given panel. Also, I need to check e.g. if it was selected. Has anyone some advice on how I should search for a proper container of these items? Re: Weird frame around test indicator I agree. No impact. Actually, the last TC versions work stable for us The only effect is that I can't shake the feeling that I develop tests using broken software. Re: Azure pipline yaml cancel TC run The actual problem was with jobs conditions. I've added the "and(succeededOrFailed() , ..." and now TC is stopped when the pipeline is canceled. The only nuance is that my AfterTests operations are not performed. But that is acceptable for the scenarios in which I will cancel that pipeline. Azure pipline yaml cancel TC run GIVEN azure devops yaml file pipeline devided on two jobs firstJob - some tasks preparing environment, install last version, etc secondJob - some more preparations tasks and run tests task Test run task is a runTests.ps1 script wich run the "C:\Program Files \...\TestComplete.exe" with parametrs (desired project, etc) WHEN I cancel the build THEN I want testcomplete to stop running the tests But I cant figure out how make test complete (running on pool agent) know that he should make Runner.Stop(false) I'm thinking to read from file in the project sources folder, but how can i write to that file from pipelines when build cancels Did anyone solved the similar problem? SolvedRe: confirm about error :The operation cannot be performed, because the user session is disconnect I can't get it. #1. Are you running the tests on your local machine (Machine_1)? Or #2. Are you running the tests on another local machine (Machine2), where you are connected by RDP from (Machine_1)? IF your case is #2 THEN you should configure these regedit staff on Machine_1 where the RDP session is opened to the Machine_2 Also, did you try the solution with WSL? Works like magic for me. My fault I send you the wrong script in the previous comment. I actually use the inline script in the YAML file: - bash: | remmina #INSERT YOUR PATH TO .remmina SESSION CONFIG FILE HERE displayName: Take RDP session on WSL timeoutInMinutes: 1 continueOnError: true It will always fail by timeout unfortunately, or last forever if you not using the timeout property, so that's why the continueOnErro is here. I just did not invest enough time to make a proper script that will release remmina process and continue the pipeline Re: functions stopped running (JS) Remembered later that there is an old piece of code that requires cofig.dev.json file which is gitignored And this code runs before all other functions and logs no error to TC logs unfortunately. something like this: (function setConfig() { /*some code here that uses config.dev.json*/ })() The saddest, in this case, is that I have a Deja Vu with this problem. Seems that I need to spend time refactoring this functions stopped running (JS) I've tried to rename the project suite yesterday and move it to a different folder in Git. After that, I started receiving "ReferenceError: helper is not defined" message from my 'events,js' file Code there looks like this: const helper = require('helper'); /** Param {object} Sender*/ function GeneralEvents_OnStartTest(Sender) { if (!helper.isTest()) return true; } I did not commit these changes, so I had the last stable version in Git. I tried deleting the folder and cloning it from repository. Then I even tried to reinstall test complete and restart the OS. It did not help. After I've deleting events.js in order to try runing any function that does not require any other functions from different files Now when I run that test function that just logs a message and nothing else: The run is started, and then immediately finished. No errors are posted to the logs, but the message is not posted also. Looks like It just doesn't run the code inside the function At the same time same project works fine when run from the pipeline on our test environment. SolvedRe: confirm about error :The operation cannot be performed, because the user session is disconnect I've come up with a WSL2 solution. WSL with Ubuntu and remmina app preconfigured to connect to the test environment The script below is run from the pipeline to activate remmina session REMINNA_FILE_PATH= 'PATH TO YOUR .remmina FILE HERE' EXPECTED_ERROR='PDU_TYPE_DATA' echo $(date)'Started *** *** *** *** *** *** *** ***' cat /dev/null >nohup.out nohup remmina $REMINNA_FILE_PATH & disown if timeout 30 tail -n 100 -f ./nohup.out | grep --line-buffered -m 1 $EXPECTED_ERROR; then echo $(date) $EXPECTED_ERROR 'catched' $RVALUE cat /dev/null >nohup.out exit 0 else echo $(date) $EXPECTED_ERROR 'not catched' $RVALUE cat /dev/null >nohup.out exit 1 fi The issue I didn't figure out: The script continues running while the session is active so I just set a 1-minute timeout for this operation in the pipeline. BTW It would be cool If someone could give advice, on how to continue running the pipeline after the specific error was caught in the script