| || |
Does QTP cache object properties?
during test of a .Net application (no QC) I have the following problem:
QTP exception while working on buttons or panes "(parent) object not visible/enabled" although the corresponding TOProperty read out immediately before has the value "True".
Stopping the test and proceeding manually works fine.
So I'm almost convinced that QTP stores object properties somewhere for internally later reuse.
Has anyone encountered the effect before or does someone know how to force QTP to release/update OR object properties?
There is a slightly different thread on this: Button enabled