Your 2 cents on developing QTP material
I am in process to compile QTP/UFT material.
I felt that beginners struggle a lot to find the suitable starting. My focus is on beginner to medium level automaters.
Point 1: It will be great to know the multi-dimension thought on what should be ingredient in the material to make it more interesting and conceptually binding.
Point 2: Also which topic you want to incorporate is also helpful to suggest.
For example in Point-1 I thought : Incorporate case study, Comic figures
Few things in Point-2 : Object, Synchronization, filesystem, automation need and so on...
You suggestion is all welcome
Admin: I am not sure If you want to move this thread to QTP/UFT forum.
I would find out the most tedious testing task. Perhaps something repetitive and eye straining that they have had to do on each release.
Go write the QTP code on your own.
Then make some funny videos of the manual tester being frustrated. Then show how to quickly write the code in front of the audience in real time(maybe only 10 lines). Then show the rest of the video with the same manual tester drinking a from a coconut under an umbrella in the office while the script prints out passes and fails. Show his/her big smiling face as the fade out.
I think it would be fun!
Yes showing the worth of automation and ROI analysis is good point.
Like kind of material we wanted when we were started our career a decade ago....
few topic like - QTP internals and tracing, FTP, log4j, Unix and UFT, QTP common troubleshooting, DOM , QTP and settings of browser, windows (UAC and so on), OLE , COM and .Netfactory, reserve objects....
What else automater may need in initial stage of learning in material in terms of content and depiction of that ? any thought...
Why don't you have them go through the tutorial to get them familiar with the tool. Also a good book to read, QTP Unplugged.
yes tutorial is already one aspect of the material but not solely end there.
Yeah the tutorial and help file cover the QTP specific operations pretty well. Rarely see folks struggling with QTP commands, it's the underlying vbs language. Especially testers who find themselves in automation without ever having had any computer science classes or anything to learn programming.
Inside of QTP I usually feel comfortable. The time I do have trouble is when the documentation is scattered. For example: The DataBase() method can add, delete, rename sheets. Each time I work with this, I have to scramble all over to find out how to do it. If you know the number of the sheet but want the name of it, I have to keep coming back to this board to find the answer.
On the outside of QTP, knowing how to communicate with an Excel workbook and sheets falls out of my memory. Other applications and objects are part of our work environment, but I have to start from scratch or look for old examples.