Forum Discussion

MichaelMcFarlan's avatar
MichaelMcFarlan
Contributor
14 years ago

Object browser randomly resets itself

I use the Object browser extensively while writing scripts but for some reason it randomly resets. By reset I mean the whole treeview collapses so that I only see the parent Sys item with the little windows flag. I have a filter active that only shows me the program I'm working with. I wouldn't mind very much if all I had to was expand it and click back to where I was, but due to being many layers deep down in some of the objects I have to first find a specific form, and then trace my way through multiple (sometimes ~10 layers deep) objects until I get back to where I was.



This has been happening for a while and I've been constantly looking for some sort of cause but I haven't found one. Sometimes it happens when the object brower (and Testcomplete) aren't even active. Sometimes it happens when I'm in the middle of using the object browser. Sometimes it will happen various times in a few seconds (e.g. I'm using the browser, it resets, I start to go back to where I want and it resets before I get almost anywhere).  And lastly sometimes it won't happen for days.



I don't know much about how the object browser works, but could it the program I'm using is resetting it somehow? Or is this a testcomplete issue?

6 Replies

  • MichaelMcFarlan's avatar
    MichaelMcFarlan
    Contributor
    14 years ago
    For some reason today it's happening every single time I try using the object browser making coding come to a standstill. Also, I suppose I should mention the obvious, the program I'm testing is always left open.
  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    14 years ago
    You're not hitting "CTRL-R" repeatedly, are you, in your automation work?  That automatically refreshes the Object Browser if it's the current window.



    Also, what version of TestComplete are you using?  I'm using Enterprise 8.20 and I'm not experiencing that behavior.



    Thirdly, what type of application are you work with?  Is it a web page that has an auto-refresh on it?
  • MichaelMcFarlan's avatar
    MichaelMcFarlan
    Contributor
    14 years ago
    Thanks for your ideas. Ctrl-R definitely isn't it, I've never used that before and lots of times the object browser isn't the active window when it resets itself. I've also got Enterprise 8.2, which might mean this is being caused by something on my computer. The program is a Delphi application. I can't really imagine why it would be constantly resetting its internal objects, plus since lots of times I've gone days without this happening I don't think that's the case.



    Computer info: Windows 7 Business sp1, 64 bit, 6gbs ddr2 ram, 2 quad-core 2.67ghz server processors, test complete version 8.20.538.7





    My only remaining clue (overstatement really, more of a shot in the dark) that I just noticed today is that I left my computer on last night so maybe that is in some very weird way explaining why the object browser is resetting itself so much today. I'm going to try a reset and see if it works any better.
  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    14 years ago
    That actually sounds plausible, especially if your machine went to sleep overnight... could be that TC is just trying to get caught up and is having some serious hiccups with restoring up...
  • MichaelMcFarlan's avatar
    MichaelMcFarlan
    Contributor
    14 years ago
    Restarting my computer doesn't seem to have helped any. The object browser is still resetting itself fairly often. I would really appreciate some advice on how to make this stop because having to dig through several layers of objects every time I want to check on a variable or two is a waste of time.
  • AlexeyKolosov's avatar
    AlexeyKolosov
    Icon for Staff rankStaff
    14 years ago

    Hello Michael,


    We've been unable to reproduce the behavior here.

    There is a chance that the issue is caused by some exception in TestComplete. To check this assumption and trace the exception if the assumption is correct, please use AQtime Standard, our free profiling tool. AQtime can trace exceptions and show their call stack. Data generated by AQtime can help our developers find the cause of the problem.

    Here are the steps:


    1. Download AQtime Standard


    2. Install the tool.


    3. Start AQtime with the -NotOpenApp command-line argument. For example, you can use the following command line:

    "c:\Program Files\SmartBear\AQtime 7\Bin\AQtime.exe" -NotOpenApp


    4. Select the 'File | New Project From Module...' main menu item.


    5. In the Open File dialog, select the TestComplete.exe file and click Open.


    6. Take a look at the AQtime toolbar - there is a combo box. Open it and select the "Tracing | Exception Trace Profiler" item.


    7. Select the "Options | Options..." main menu command - the Options dialog will appear.


    8. Set the "Profiling Time | Event View | General | Exceptions | Depth shown" setting to 100 and click OK.


    9. Click the Run toolbar button (the green arrow) or press F5 to start the profiling.


    10. AQtime will start TestComplete and trace all exceptions that will occur in the application until it is closed.


    11. Reproduce the problem with the Object Browser panel.


    12. After the problem occurs, right-click somewhere within the Event View panel (it is opened by default at the bottom of AQtime's window) and select the 'Save All...' item.


    13. Save the panel's contents to an HTML file and send the file directly to our support team.