HP UFT - Keyword view Vs Editor view

Pavan Lalwani
A free video tutorial from Pavan Lalwani
Freelancer Instructor
4.5 instructor rating • 8 courses • 64,971 students

Learn more from the full course

HP UFT - Basic to Intermediate

Automation testing with HP Unified Functional Testing

04:46:37 of on-demand video • Updated June 2018

  • Download HP UFT
  • Installation of HP UFT
  • Record and Run test
  • Functional testing
  • Actions
  • Objects
  • Types of Recording
English [Auto] Welcome back, indiscrete. We'll see what is the difference between keyword view and you will also see what is the similarity between keyword view and the adjective. So first of all, open the same script which I've done the previous video. That's the same story which is given here. Now, this window is nothing but the editor view. So I have written the scripting. I've not written actually I've just recorded. And the VP script steps up automatically generating this list. So what is the meaning of the script? What it says? Let us see. So first of all, I just try to explain it with the help of this active screen. So folks are go to this view menu board and then select the option as active screen from here so we can select this active screen. I'll get the screen here. Active screen. So now if I keep my focus on the first step, I'm not an automation engineer. I'm just a manual tester. If I keep my focus on the first step and the active screen, the user name is highlighted. So this belongs to this particular object that is username keep Michelsen on the second script, which is given second line. So it says this is related to the password object third line. It says it is related to the okay button object. So we have this active screen, at least I can identify it. This is related to that particular object, not same if I go to this view menu board and if I click on this keyword view and what geddis if I click on this second language is given us Agent Naem, I'll be selecting the same dialog box, same object in the active screen. And if I click on this password object in this place and if you observe the password text box, the password object is selected in the active screen. So here I can conclude, yet I can see the editor is equal to your keyword view editor review and give view. Both are similar. The steps are just formatted so that a person with the coding knowledge and understanding the greater part without the coding knowledge and understanding the keyword. You said let us try to understand the keyword by itself. If you observe here, it's given us HP, my plate sample application. It's a window. If you see there's a window, the icon is about the window sill below that window. If you see the Asian name and the icon is given as the Bensel button, if you observe the pencil button is given here Bensel button, it says it is nothing but a data box. Same v e password is also an added box, which is given a pencil button below the password textbook. The pattern is given into a small rectangle, which is nothing but a button symbol. So one application will have multiple types of objects. Added box, button, checkbox, radio button, dropdown list, many things. So based on the object type, the icon also keeps on changing. Same thing. Now if you see the operations menu board agent in the edit box, you'll be setting something some data into that. So if you see set and John is given, so if you try to form a sentence of this particular action, it says enter John in the Asian name added box seems a place for the second. Second, it says enter the encrypted password in deposit box. Why this is an encrypted password? Because if you see the value column, it is encrypted in the different format. So therefore it is given at the third step. Say the same thing, click on the OK button itself. And if you observe the operation menu button says the click button is given the same method. If you see if you follow the next languages, my sample application, you have to close it. And in the documentation part it is closed. DHP, my flight sample application. So if you are on manual tester, you will have an idea about the test case where you have the test case objective, very the preconditions steps to execute a data column, expected results, actual results. Same thing has been formatted in the form of the automation in the key value packets. So if I want to go back to the edit review so I can go to The View menu board and click on this a little part and I'll be coming to the end of the required futsal, what exactly it says. I'll try to explain you the first line. It says WP off window and the name of the window is given a double calls with the brackets of WP of what is the full form of WP. If it's nothing but Windows Presentation Foundation, it is the environment. It's a framework developed by the document framework framework itself. Not if I'm using a calculator. It can be considered as a Windows application. If I'm using Google or G.M. or Yahoo! Or Facebook anything, it can be construed as a Web based application sameway if it's a Windows presentation foundation. So I'm using this as WP a window. And if you see there's a document. So this is my flight sample application that is an the WP off window on that window. There are multiple objects in the box, checkbox, radio button. In this example, if you see there's a WP edit, that means there's a box. The name of the box is nothing but the agent name. So whatever the name is given in the red color double codes, that is the actual object name which is given here. So that's the object name. That is each name password in October. And these are the. Object names dot set is nothing but an operation you're doing on that particular object and in the course that the value of your entering it. So S.V., if you if you try to understand it, this is nothing but apparent object and dot followed by the object, dot by the action or by the operation. What you perform is similar to the third one. It says this the apparent application, which is an apparent object on that. You have this button and that button. You're performing some operation that is clicking on displays. So these are nothing but the editor part. And if you are a developer, if you're not also a developer, you can easily understand this part. So I hope you understood what the similarity between the interview and, you know, the key word itself. That means both one and the same. That's the similarity. If you keep your cursor any place in the act, you'll be getting the images, the snapshot with the highlighted objects and the differences. For the developers, it is easy to understand the entity, but for the testers manual, that's the key. What was important, they can easily understand. But the manual testers, they cannot run away longer from the editor part because at the end they're jumping to automation. They have to learn the scripting, knowledge, scripting, knowledge or the scripting, but also will be covered in the coming videos right from the scratch so that any newcomer from the manual testing and easy easily understand this part also. So I hope you understood. That's all for this video.