Technovation By SKS

  1 Output  In my previous chapter, I discussed about QTP Checkpoints which is a very handy utility for comparing the expected and actual result. This chapter covers the topic of OUTPUT utility available in QTP. This utility is also very handy in capturing the run time values from the application under test. You will use OUTPUT utility where in you are testing and automating an end to end test scenario. In such a case output of one module is an input to next module. An end to end Business Scenario example is given below: Validate that user is able to book and cancel the flight ticket Step1- Navigate to booking site The user navigated to booking site Step 2- Enter valid login credentials The system allowed login and display the flight booking page Step 3- Fill the Booking Information & Submit the form The system generate a unique PNR number once data is processed

“Let me first say sorry to all my readers for such a long wait for Chapter 6. It was totally my fault for such a long wait. I promise to all my readers that now they do not have to wait for so long for next chapter and every month I am going to publish 2 Articles. With this pledge, let get started with Chapter 6.” 1 Checkpoint In my previous chapter, I touch base with checkpoint but not in great detail. In this Chapter I am going to talk only about Check Points/Verification Points/Validation Points. First I will describe what is a Checkpoint? Let me explain the concept of Checkpoint with an example: See the below scenario with expected result for each step. The third column provides the information on where QTP checkpoint can be used. Validate the layout of login page Step1- Navigate to page The user navigated to login page Step 2- Verify user name input field The User Name field is visible and editable