joe_brooks
Contributor
Joined 3 years ago
User Profile
User Widgets
Contributions
Re: Issues with dropdowns and ClickItem() not working if the dropdown opens in the up direction
I would like to note that SmartBear has finally addressed our ClickItem issues in TC 15.63.22. The correct item is selected, the direction in which the dropdown list opens does not prevent a successful selection by causing an error, the necessary events are fired and the ClickItem step runs reasonably quickly (<= 1 second). It is obvious from watching tests run that it is not a true ClickItem that is being performed, but the way in which it is being simulated now is working for us.691Views3likes0CommentsRe: The tested window (or control) has been deleted
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.14Views0likes0CommentsRe: The tested window (or control) has been deleted
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.73Views0likes6CommentsRe: Issues with dropdowns and ClickItem() not working if the dropdown opens in the up direction
I assume you mean that you are using v14.93, not v4.93. I have been working with SmartBear on a support case for this issue (actually several ClickItem issues), and they have indicated that they are working on a fix for the issue. When they do issue a fix for this issue, it will be in version 15, probably v15.59 or later, so you will have to upgrade to v15 to access the fix.432Views0likes0CommentsRe: Issues with dropdowns and ClickItem() not working if the dropdown opens in the up direction
Agreed that we need a resolution and that employing the workaround is not ideal. I have been working with SmartBear on a support case for this issue (actually several ClickItem issues), and they have indicated that they are working on a fix for the issue. However, the workaround can be made to work in all cases if you replace the ClickItem step with two Keys steps, where the first Keys step sends the press of the Home key to the dropdown box, and the second Keys step sends the full text of the dropdown list item to be selected.238Views0likes0CommentsRe: Issues with dropdowns and ClickItem() not working if the dropdown opens in the up direction
juliemorris No, the ClickItem() issue that I reported has not been fixed yet. However, I did finally receive confirmation from SmartBear's Customer Care that SmartBear understands the issue that we're experiencing and that it has been forwarded to their developers. My support ticket has progressed to the status of "Researching" as of July 27th, 2023. Customer Care is supposed to reach out to me as soon as they have an update on the issue. As of right now, the best version of TestComplete with regard to how ClickItem functions is still 15.51.30, and we are still on that version. There have been two subsequent updates to TestComplete, 15.52.2 and 15.53.2. Both use very odd and slow implementations of the ClickItem() method. ClickItem test steps take an average of 3x longer to execute in 15.53, and 15.52 is even slower. This is a big issue for us as our tests have lots of ClickItem steps. Neither 15.52.2 nor 15.53.2 has any impact on the ClickItem() issue described in this post, nor do they seem to provide any other benefits, so we will remain on 15.51.30 until both this issue and the performance / behavior issues introduced in 15.52.2 and 15.53.2 are resolved.1.2KViews2likes2CommentsRe: TestComplete issues with Chrome 113
Upgrading to TC 15.51.30 has resolved this issue for me as well. I think Pawel's (PMularczyk) post from 05-30-2023 11:23 AM should be marked as the answer to this issue, as TC 15.51.30 appears to have fixes for all of the issues reported on this thread.651Views0likes0CommentsRe: Issues with TestComplete 15.51 playing back existing tests that run fine on TC 15.50
TC 15.51.30 has been released and contains the fixes needed to resolve this issue. We are no longer experiencing the issue reported at the top of this thread after upgrading to this version.424Views0likes0CommentsRe: Issues with TestComplete 15.51 playing back existing tests that run fine on TC 15.50
gabedemoura Thank you for replying. I have tried updating to the latest version of TestComplete. Specifically, I have tried: TC 15.51.4 TC 15.51.18 TC 15.51.26 All three versions do not work for me. The latest version of TestComplete that works for me is 15.50.3.432Views1like0Comments