[BUG] Object Properties doesn't work in the code when an object has RegExp

Another very handy feature in QTP is that you can right over your code, where you have a Browser(...).Page(...).Link(...) object and choose "Object properties" option, which shows you a small screen to view its properties and a button to take directly into the Objects Repository, with your object selected.

Well, in QTP nothing can be too good.

Say in our example above, the .Link(...) has a regular expression such as .Link("text:=Search"). In this case,  the option "Object Properties" in right click menu will be disabled for objects Browser() and Page() objects. Again, I have no idea why.

And even worse, if your Browser(...).Page(...).Link(...) is part of an IF statement (or any other statement), then this option won't be available at all. No properties will be available for any object.

[BUG] Function Browser().FullScreen() is not working in QTP 11

Simply put. Function Browser().FullScreen() is not working in QTP 11.

Every time I try the FullScreen() command, I get a "General run error". As if a "General" would have "errors" during his daily "runs". #worst_joke_ever

Nothing else to say.

[BUG] When did an error is actually expeted? (UPDATED!)

Honestly, no errors should be expected in any application, right? Everything should work flawlessly. But in the real world this is not what happens.

Not even with QTP.

Yesterday, I tried to check out an Object Repository (aka OR) from Quality Center which was not checked out to any one, when I came across something unexpected.

Let's be honest. What good does an error message like these ones do? No answer is required.

Well, let me tell you that I tried several different approaches to fix this problem, all in vain. Closed QTP up and restarted it. Didn't work. Closed all programs, restarted my computer. Didn't work.

Turns out that my coworker edited the same OR few minutes before me, and did the check out/check in normally. After the fact, I tried to check it out on my PC and ended up with these error messages.

Solution: **apparently** what happened is that my coworker's QTP silently crashed after editing the OR and didn't freed it up correctly. When closing his QTP down, it displayed a memory leak problem which as probably the main problem.

After making sure his QTP was a 100% dead on his PC, the OR was MAGICALLY available for checkouts as expected.

#facepalm.


UPDATE: a new message (or not) was reported by my coworker, on QTP 11. I swear, this is NOT fake!