Ideal Tactics in QTP Automation

0
25
Spread the love
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  

  • Commence your automation operate only when AUT (Software Beneath Test) is stable. i-e You must have completed original round of handbook tests in advance of starting up QTP automation task.
  • Use reusable actions where ever possible.
  • Really don’t duplicate and paste checkpoints when you would like to test same issue in more than one spots. Alternatively, make separate checkpoints. Due to the fact manipulating checkpoints in QTP is not feasible or it will be tough.
  • Open browser/application soon after opening QTP.
  • Your vbscript features should not have any tricky coded object names, the identify of the objects really should be passed as purpose argument.
  • Use Shared Object Repository. My suggestion is never use DP (Descriptive Programming) which will enhance your routine maintenance work.
  • In advance of incorporating any object to Object Repository, established up suitable object identification properties (in Tools->ObjectIdentification) if you feel that default identification properties are not appropriate for you application. If you do it following incorporating some objects to the Item Repository then you may possibly confront concerns linked to getting many Examination objects in Object Repository for a one genuine Object.
  • Open up QTP making use of Automation object product. You can do it just by producing (even you are having ‘generate script’ solution in the QTP IDE itself) very simple .vbs file, and then open QTP just by double clicking this .vbs file. It is quite extremely essential if you are acquiring your scripts in a single equipment/setting and planning to operate/execute it in a different setting. By using Automation Object product we are earning certain that all the IDE settings (e.g Object identification homes) that are modified in progress surroundings are propagated to the execution environment also
  • Often use Reference/Relative path when calling any exterior reusable action rather of working with absolute/total path, Or else the script will fall short when positioning it in diverse route.
  • Remember to consider backup of Object Repositories ahead of merging object repositories.
  • Put correct inline remarks and also place summary responses (description, enter & output parameters,dependency, writer) at beginning of the Test. In the responses remember to mention about execution/knowledge move.
  • Rename the Objects in Item Repository to have good this means for them. For the reason that the default name offered by incorporating the objects by recording or manually may well not be superior/meaningful.
  • Give consideration to synchronization (i-e use of sync,waitproperty, exist). And also use normal expression where ever required. If not regularity of script execution will be influenced.
  • Use recovery scenario to manage any sudden behaviour (e.g exhibiting pop-up windows occasionally) of the application.



Supply by Rajamanickam Antonimuthu

Don't miss out!
Subscribe To Newsletter

Receive top technical news, lesson ideas, travel tips and more!

Invalid email address
Give it a try. You can unsubscribe at any time.

Spread the love
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  

LEAVE A REPLY

Please enter your comment!
Please enter your name here