Contributions
Re: ClickItem only works once per test
I reached out to support and on Friday they were able to give me a patch to manually apply that fixed this issue for me. It sounds like this will be resolved in the next major update in a couple weeks. 8/7/2023 is what was mentioned in my communication with support.915Views1like0CommentsRe: ClickItem only works once per test
In case anyone was following along. I was told that the next update should fix this issue. It was supposed to be out on 7/5/2023 but does not look like that happened. I will try to remember to update this post when the update releases and I can verify my issue is resolved.10 months agoPlace TestComplete QuestionsTestComplete Questions960Views0likes2CommentsClickItem only works once per test
I know ClickItem has been having issues since 15.51 came out, so we have been running 15.49. I saw 15.52 is out so I figured I would give the latest a try. I am on 15.52.2.7 x64. I am still having trouble with ClickItem failing to run on my tests. It seems that it is only happening if you run a ClickItem command on the same ComboBox in the same test. If I run a test that only touches that combo box a single time, it works fine. If the test clicks on the combo box (to open the list) then tries to do a ClickItem it fails. If I disable that click before the ClickItem it works fine. If the test runs a ClickItem on a combo box it works, then if the same test tries to circle back and tries to run another ClickItem it fails with this error: An error occurred. Possible reasons: 1. The application stopped responding. 2. The application was compiled incorrectly (see the Open Applications topic in the help system). 3. An error occurred in TestComplete/TestExecute. Technical information: 515 0x80020003 (Member not found.) . I verified the ClickItem command is not incorrect by disabling the first interaction with that combo box, now the command that was failing works fine, but of course the test fails on the 3rd attempt to interact with that combo box. Anyone else seeing a similar issue? Edit: This is on a .Net Windows ApplicationSolved1.1KViews0likes7CommentsRe: Multiple Issues with TestComplete 15.51.4.7
Thanks for the tip. I was considering going in and using the keys function to bypass all the ClickItems. It is unfortunate that we might need to do that though. Not even two weeks ago ClickItem actually found an issue with dropdowns in our .Net app. They were not actually clickable, but you could use the KB to select your item. It is nice to have a mix of both functions for reasons like that. I think we may just downgrade to the last version until a new update is released. Just having trouble getting into our license account currently, so that is not really possible. When it rains it pours right? hah!12 months agoPlace TestComplete QuestionsTestComplete Questions986Views0likes0CommentsRe: Multiple Issues with TestComplete 15.51.4.7
Also having the same issues with ClickItem not working on Web or on a .Net App. In web, it seems like it tries to click on the item in the list, but then just spams the down arrow until it hits the bottom of the list, that of course breaks the rest of the test when the proper item is not being selected. In .Net it just hard fails with this error: Possible reasons: 1. The application stopped responding. 2. The application was compiled incorrectly (see the Open Applications topic in the help system). 3. An error occurred in TestComplete/TestExecute. Technical information: 515 0x80020003 (Member not found.) .12 months agoPlace TestComplete QuestionsTestComplete Questions1KViews0likes0CommentsRe: typeinfo.dat not checking out with source control after updating to TC15.
After doing some more testing, this appears to have also been happening before TC15, we just didn't notice because we had not made changes to the name mappings for a little while. I just opened a test and created a new onscreen action and pointed at a random thing, then tried to check in. It is failing to check in because of this error: Anyone have any thoughts on why our tests are failing to check in when we change name mappings? If typeinfo.dat is not part of Source Control, why is TC attempting to edit it when when change name mappings? Do we have something misconfigured?721Views0likes1Commenttypeinfo.dat not checking out with source control after updating to TC15.
Has anyone else been having issues with check-out and editing tests since upgrading to TC15? It seems that it no longer checks out the NameMapping\typeinfo.dat and so if we try to check in our changes we get access denied, then the execution plan gets wiped out. If I pull up VS Source Control and check out that file (after checking out the rest from TC) then I can make edits and check them in just fine. It even checks in the TypeInfo.dat file.753Views0likes3Comments