We just got back from some advanced training, have my team lead and I. We were training with a consulting firm in Greensboro called Questcon, and this was most rewarding. The advanced training was well given, and the discussion generated between us and the team there was most excellent. I would recommend them highly to anyone seeking something beyond the regular "say-show-say" approach to QTP training. We discussed the topics, but also discussed how these topics applied to everyday work, and our...

• Share This Post:
• 
• 
• 

My team lead and I have talked with our VP, and we are abandoning the Octane engine in favour of using QTP the way it is intended to be used. So, I am now building a re-useable testing component framework from the ground up. Sure will save us some time later in the process. QTP is by no means perfect, but now I don't have the extra layer of error-causing code in the way. I also just finished a coding standard we will use going forward. Should help make our peer reviews easier, and our code more maintainable....

• Share This Post:
• 
• 
• 

Well, I have finally found time to get my object repository editor working well. It's what I call in a "internal tool beta" state, which means it's not very pretty but works well. Since there will be only two of us using it, seems like a fine state. I know, I know....any code worth writing is worth writing nicely. However, given the timeframe in which I've had to work, I've done a fair job. Now, that's not to say it won't benefit from some nice refactoring. As a matter of fact, I've refactored a...

• Share This Post:
• 
• 
• 

Turns out that I still had an old copy of VB6 that I actually own (haven't seen it in years), so installed that it seems to be working fine with the typelib for the QTP Repository Utility. I will be documenting heck out of this process once I get it written, though. No way I want to have to figure this out again

• Share This Post:
• 
• 
• 

Been working on the tool I mentioned before to manage the object repository in a previous post. I dutifully fired up the VB.Net IDE, and began work. However, there are some snags: 1) The tool API is a COM object. Not a big deal, but a little unfortunate. Shouldn't be a problem, I was thinking. 2) The API was written to work in VBScript...not VB.Net Issue 1) isn't a huge deal, but 2) is. Why? Well, there are two things causing me grief: 1) One of the methods off of the main object accepts two optional...

• Share This Post:
• 
• 
•