I am a beginner in QTP.
Regarding your question about QTP not recognizing certain objects, etc.. can you be more specific what you are trying to test, and what kind of objects you are keeping in your mind, etc? Then people in this forum should be able to answer specifically and clearly.
The application I test is a web app. Almost all the pages are built on the fly and its all custom. The page layout, controls (form fields and their order), everything changes based on configuration as well as data. Every client will have their own preference on layout of panels, order and style of data/form-fields that appear on panels, etc. For this I had to do descriptive programming like: for example, if I am testing a process, which boils down to few clicks on few controls across few pages, then using QTP scripting, I check if the control exists then click on it and if a form field exists then fill data etc. If not exists and its required then record error, otherwise skip the step etc.
For static controls and objects, we can pretty much do record/play based testing. Only for dynamically changing controls and objects, we need descriptive programming.
There is another thing, say, we record our test for your application version 3.1, now your application 4.0 is released and one or more controls or objects changed (added/deleted/modified), we obviously need to re work on the test. Because the application is not anymore the same as before. So we are testing a different process. It is same as the scenario where the tester, doing manual testing, needs to learn some things new due to these changes.
Also I use recovery scenarios, where if any failures, beyond all this programming, happens, test process is told to go to next iteration. Recovery scenarios can be setup, at this unexpected occasion, to stop the test, or to go to next step of the test, etc.
But if your pages changes
Also my workplace do not have HP Quality center product. We just have QTP. Probably you can do a whole lot more with this Quality center.
Regarding your question about QTP not recognizing certain objects, etc.. can you be more specific what you are trying to test, and what kind of objects you are keeping in your mind, etc? Then people in this forum should be able to answer specifically and clearly.
The application I test is a web app. Almost all the pages are built on the fly and its all custom. The page layout, controls (form fields and their order), everything changes based on configuration as well as data. Every client will have their own preference on layout of panels, order and style of data/form-fields that appear on panels, etc. For this I had to do descriptive programming like: for example, if I am testing a process, which boils down to few clicks on few controls across few pages, then using QTP scripting, I check if the control exists then click on it and if a form field exists then fill data etc. If not exists and its required then record error, otherwise skip the step etc.
For static controls and objects, we can pretty much do record/play based testing. Only for dynamically changing controls and objects, we need descriptive programming.
There is another thing, say, we record our test for your application version 3.1, now your application 4.0 is released and one or more controls or objects changed (added/deleted/modified), we obviously need to re work on the test. Because the application is not anymore the same as before. So we are testing a different process. It is same as the scenario where the tester, doing manual testing, needs to learn some things new due to these changes.
Also I use recovery scenarios, where if any failures, beyond all this programming, happens, test process is told to go to next iteration. Recovery scenarios can be setup, at this unexpected occasion, to stop the test, or to go to next step of the test, etc.
But if your pages changes
Also my workplace do not have HP Quality center product. We just have QTP. Probably you can do a whole lot more with this Quality center.
