Forum Discussion
This issue has resurfaced. Starting with TC 15.56, every version released up through TC 15.60 has had this same issue.
To be clear, that includes 15.56, 15.57, 15.58, 15.59 and 15.60.
We have a support issue open with SmartBear for a ClickItem() issue. They were supposed to deliver a fix for it in 15.59, but we're unable to tell if it is fixed because this issue blocks us from running our tests to find out if it is fixed for us.
We have been downloading and trying updates to every version released since 15.51.30, the last stable and usable version of TC for us. TC 15.52, 15.53, 15.54 and 15.55 do not deal with ClickItem() statements properly or efficiently. TC 15.56, 15.57, 15.58, 15.59 and 15.60 have been entirely unusable, exactly as noted above for 15.51.18. We have reported the same to SmartBear for each release, but they continue to create updates that we cannot run.
Browser version has been irrelevant for each of these releases. We have experienced the same issue using every version of Chrome from 113 to 120.0.6099.225, the latest version as of today, January 18th, 2024.
This set of issues has been going on for about 9 months now and they are apparently nowhere near solving it, from what I can tell. We've been very patient, but we need a resolution to this soon. We can't be stuck on 15.51.30 forever.
- rraghvani12 months agoChampion Level 3
I'm using v15.55.53.7, ClickItem method is working using scripts, although the behaviour is not correct. I'm not going to upgrade any time soon.
- DBowerman12 months agoOccasional Contributor
I had upgraded to 15.59 on Tuesday (1/16) and it was working great! I had no issue with my Web-based test cases running on this version, until today. Today, I'm not getting "The tested window (or control) has been deleted " error. Nothing changed except that I shut down my PC over night. I'm thinking this might be a "Chrome/TestComplete compatibility issue when using multiple monitor" issue. Today, Chrome version is 120.0.6099.225 (not sure what it was yesteday, because we have no control over when a new version is released/downloaded, but based on the above post the latest version was release yesterday). I'm assuming Chrome was updated when I shut down my PC overnight.
Here is what I seeing: Using TC version 15.59, Chrome version 120.0.6099.225, and having mulitiple monitors enabled, I get the "tested window (or control) has been deleted) error.
However, if configure my PC to only use one monitor the test case complete successfully.
- rraghvani11 months agoChampion Level 3
I remember reading somewhere that multi monitors and high resolution is not supported by TC.
- DBowerman11 months agoOccasional Contributor
I have been using mutiple monitors for years. Have not had an issue until now. I have a case opened with TC regarding this issue. I'll ask.
- joe_brooks11 months agoContributor
I've thoroughly retested this issue this week, and I've discovered several things during testing. I tested TC 15.51.30 (the version we currently use), 15.56, 15.57, 15.58, 15.59 and 15.60 using Chrome 120.
- The issue does not occur on 15.51.30. Previous testing has also shown that the issue did not occur for us on 15.52, 15.53, 15.54 or 15.55. However, ClickItem() issues kept us from adopting any versions after 15.51.30.
- This issue is definitely related to multiple monitor setups and occurs when running TC 15.56, 15.57, 15.58, 15.59 and 15.60. When running these TC versions on a single-monitor setup, this error does not occur. High resolutions, from Full HD (1920x1080) up to 4K (3840x2160), were tested successfully with no error occurring.
- With a two-monitor setup, with the side monitor on the left, the issue occurs when running TC and the browser on the side monitor. Running TC and the browser on the main monitor did not cause the error to occur.
- With a three-monitor setup, the issue was much worse.
- For TC 15.57, 15.58, 15.59 and 15.60, the error occurred on all monitors.
- For TC 15.56,
- The error did not occur when TC and the browser were run on the left side-monitor.
- Running TC and the browser on the main monitor caused the error to occur.
- I did not test the right side-monitor because mine is in portrait orientation.
Yesterday, Chrome updated itself to v121.0.6167.85. Running TC 15.60 with Chrome 121 appears to have fixed the issue. The error no longer occurs with a three-monitor setup. I did not go back and test versions earlier than 15.60 with Chrome 121.
However, there are still unresolved ClickItem() issues in 15.52 and later versions that are worse than the ClickItem() issues in 15.51.30, so we are still staying on 15.51.30. We have a support case open to fix the ClickItem() issues, and we're still waiting for a proper fix. The changes made to ClickItem in 15.52, 15.53 and 15.59 do not work properly for us and the results are worse than the original problem we reported in 15.51.30. - The issue does not occur on 15.51.30. Previous testing has also shown that the issue did not occur for us on 15.52, 15.53, 15.54 or 15.55. However, ClickItem() issues kept us from adopting any versions after 15.51.30.
Related Content
- 2 years ago
- 10 years ago
Recent Discussions
- 6 days ago
- 6 days ago
- 9 days ago