Geeks With Blogs

News QTP and Stuff
Theo Moore Questions... Morphology? Longevity? Incept dates?
Sometimes, you just have to get get it done.

I have gotten sick of all the TONS of documents being generated on requirements for the project on which I am working. I am required to be a manual tester, and I am already pretty tired of that. Then, the requirements started coming in....OMG!

Being a diligent tester (and for traceability), I have been entering those requirements in Quality Center. It's just gotten to be a big job, so I fired up Visual Studio, determined to ease my burden. I wanted something that would rip requirements out of Word docs and then pump them into QC. I figured heck, how tough can it be?

Anyone else see where this is going?

Since the Quality Center application uses COM, you can see, no doubt, where VS 2008 would have some issues. I was trying to use Interop to get it to work, but the COM dll they have just isn't Interop friendly. After several frustrating hours of this, I realized I hadn't made any progress. So, I did the only thing I could think of doing one such short notice.

I fired up VB6, and within a couple of hours, I had a great little app that does exactly what I want. I know, I know...VB6 has tons of limitations and yes, it is waaaaay to forgiving of bad development (I have always said that it allows some extremely bad code to work on very short notice and do amazing things sometimes). Yet, for this instance, it appears it was the best tool for the job.

How about that? :-)

On another note, though, the Quality Center "object model" is terrible. It might be the worst one I've ever seen in a ton of ways. If I want to get at data in a field, for example, often I have to know the field name in the db. Yes, you heard me right. The interface developer must know db implementation details in order to get anything meaningful done.  There are a myriad of other issues...things like when attempting to create a "filtered" list of db entities (tests, folders, etc.), the value provided to the filtering mechanisim must be "SQL ready" in the sense that the filter isn't smart enough to handle things like spaces in the string, etc. Why the front-end developer is passing in SQL parameters I just can't guess.

Anyway, enough on the limitations with QC.

Lesson learned here: sometimes...SOMEtimes...the right tool for the job isn't the best tool overall.
Posted on Sunday, February 17, 2008 12:31 PM | Back to top


Comments on this post: QC in .Net?

# re: QC in .Net?
Requesting Gravatar...
Dude, that is a super cool story. Right tool, right job. Thanks for sharing!
Left by Brian C. Lanham on Feb 21, 2008 7:48 PM

Comments have been closed on this topic.
Copyright © Theo Moore | Powered by: GeeksWithBlogs.net