ContributionsMost RecentMost LikesSolutionsNamemapping with Extended Find causes onscreen objects to disappear Hi, I've noticed a problem, that only seems to pop up with extended find property turned on, where onscreen objects will disappear while TestComplete is performing it's search for the object. This also seems to coincide with additional empty windows being created for the application that can not be brought up from the task bar. Has anyone else seen this behavior? Are there any fixes short of mapping the entire object tree? Thanks! Re: How to Get 'Advanced View' Object Fields? I should mention I'm using version 12.31 and the object in question is a SWTObject(RibbonSwtCanvas) GetProperties and GetMethods both work on this object Re: How to Get 'Advanced View' Object Fields? Hi Robert, Unfortunately, I can't post a screenshot. However, when looking at the Object Spy for this object, the Fields tab is present and populated with numerous Private and Protected Fields (in Advanced View). When I select the "view basic members (Basic View)" link, the Fields tab disappears. I'm speculating that this is why the GetFields method returns null. Any thoughts? How to Get 'Advanced View' Object Fields? I'm using the following to get the object fields for a mapped object: aqObject.GetFields(Aliases.Obj, true) I'm returned 0 fields found for an object that definitely has fields. My only guess is that the GetFields method only returns the basic view fields (which the object does not have any) and does not return the advanced view fields. Is there a way to return the object's advanced view fields? Allow a Test Item's "Count" parameter to be written to via script Currently, a Test Item's "Count" property is Read-Only. I would like the ability to set this parameter via an inputs file, to allow a Test Item and all of it's children Test Items to be ran a settable # of times. A workaround is to add functions to a For loop; however, the functions are no longer separate Test Items. Re: Setting a Test Item's Count via script Thanks tristaanogre. I opened a support ticket, we'll see what happens. From what I understand of the workaround, you would create a new script or Keyword test and then within that test put a For loop to execute a different script (import the function) a settable # of times. The problem I have is that I have a parent test item along with some children test items. When I want to rerun the parent test item, I would like the children test items to be kicked off as well. So it seems the only workaround would be to add those children items to the For loop as well. The downside is that now those separate test items are being run as a single test item - which I would rather not have. Am I understanding this right? Is there a better way, in your opinion, to do this? Thanks for the help. Re: Setting a Test Item's Count via script Here you go! Setting Project Test Items Count via Script Thanks! Setting a Test Item's Count via script Hi, I've seen reference to a support ticket from 3+ years ago to add the functionality to set a Project Test Item's Count via script. Is there now a way to do this? Thanks, Brandon SolvedRe: Project Test Items Do Not Repeat Using Count When Error Is Thrown Looks like that's the issue! Thank you! P.S. for anyone else trying to figure out how to add these columns: By default, the Stop on error and Stop on exception columns are hidden on the Test Items page. To make these columns visible, right-click within the Test Items page and select Field Chooser from the context menu. Then, drag the columns from the subsequent Customization dialog to the Test Items page. Source: Stopping Tests on Errors and Exceptions - Overview Re: Project Test Items Do Not Repeat Using Count When Error Is Thrown Hi Robert, I'm using version 12.31, as far as I can tell there is only a checkbox to enable or disable this functionality for the Project (found under Playback) - I've unchecked all. What I mean by ' the test will not continue' is that I would expect the following to continue retesting Script1 and all child test items ten times, even if there was an error in Script2 or Script3. What I find is that as soon as an error is thrown, the project will continue through the remainder of the Script1 child test items but will not loop back to retest Script1 for Count 2,3, etc. > Script1 with Count = 10 > Organization Folder 1 > Script 2 > Organization Folder 2 > Script 3