Describe tasks that you performed in Quality Center.
01) Changing password.
02) Creating requirements Folder in the Requirement Section.
03) Creating or exporting requirements in the Requirement folder.
04) Convert requirements to tests in the Requirement Section.
05) Developing design steps/Test Cases in the Test Plan Section.
06) Creating templates.
07) Performing requirement coverage in the Test Plan Section.
08) Creating test sets in the Test Lab Section.
09) Importing test cases in the test sets in the Test Lab Section.
10) Executing test sets in the Test Lab Section.
11) Logging defects in the Test Lab Section.
12) Tracking defects in the Defect Section.
13) Generating graphs and reports in the Requirement / Test Plan /Test Lab/ Defect Section.
14) Creating domains.
15) Creating projects.
16) Creating users.
17) Assign users to projects.
18) Granting privs to users.
What is a Bug Life Cycle?
The duration or time span between the first time bug is found (‘New’) and closed successfully (status: ‘Closed’), rejected, postponed or deferred is called as ‘Bug/Error Life Cycle’. (Right from the first time any bug is detected till the point when the bug is fixed and closed, it is assigned various statuses which are New, Open, Reject, Reopen, Fixed-Ready for retest, Testing Passed,Testing Failed,Closed, Deferred.) Below is a life cycle that a bug can passes through: 1) A tester finds a bug and reports it to Test Lead through Quality Center with status as ‘New’.. 2) The Test lead verifies if the bug is valid or not. 3) The bug is verified and reported to development team lead with status as ‘Open’. 4) The development leader verifies if it is a valid bug. The bug is valid and the development leader assigns to a developer marking the status as ‘Assigned’. 5) The developer solves the problem and marks the bug as ‘Fixed-Ready for retest’ and passes it back to the Development leader. 6) The development leader passes on to the testing team. 7) The test leader passes it to a tester for retest. 8) Scenario-i)
The tester retests the bug and if the problem solves, the tester sends the defect to Test Lead by changing the status ‘Retest Passed’ with the comments in the comments section: ‘Testing Passed, requesting to close the defect’. The test lead closes the bug by changing the status ‘Close’.
Scenario-ii) The tester retests the bug and if the same problem persists, the tester sends the defect to Test Lead by changing the status ‘Retest Failed’ with the comments in the comments section: ‘Testing failed, requesting to reopen the defect’. The test lead reopens the bug and marks it with ‘Reopen’ status and passes back to the development team for fixing. The development leader verifies if it is a valid bug. The bug is valid and the development leader assigns to a developer marking the status as ‘Assigned’. The developer solves the problem and marks the bug as ‘Fixed-Ready for retest’ and passes it back to the Development leader. The development leader passes on to the testing team. The test leader passes it to a tester for retest. The tester retests the bug and if the problem solves, the tester sends the defect to Test Lead by changing the status ‘Retest Passed’ with the comments in the comments section: ‘Testing Passed, requesting to close the defect’. The test lead closes the bug by changing the status ‘Closed’.
9) If it is needed to Push the application to the Production and there are some cosmetic bugs still need to be fixed, the whole group (Project Manager, Team Lead, Testers, Developers, DBA, CM) decide to put the outstanding defects in the Deferred status and deploy the application in the production. After deploying the application in Production, developers fix the defects.
Write the contents or fields you have to fill-up in defects windows?
The contents of a bug are as given below: Project: Name of the project under which the testing is being carried out. Subject: Description of the bug in short that will help in identifying the bug. This generally starts with the project identifier number/string. This string should be clear enough to help the reader in anticipate the problem/defect for which the bug has been reported. Description: Detailed description of the bug. This generally includes the steps that are involved in the test case and the actual results. At the end of the summary, the step at which the test case fails is described along with the actual result obtained and expected result. Summary: This field contains some keyword information about the bug, which can help in minimizing the number of records to be searched. Detected By: Name of the tester who detected/reported the bug. Assigned To: Name of the developer who is supposed to fix the bug. Generally this field contains the name of developer group leader, who then delegates the task to member of his team, and changes the name accordingly. Test Lead: Name of leader of testing team, under whom the tester reports the bug. Detected in Version: This field contains the version information of the software application in which the bug was detected. Closed in Version: This field contains the version information of the software application in which the bug was fixed.
Reproducible: If the bug is re-generatable.Date Detected: Date at which the bug was detected and reported. Expected Date of Closure: Date at which the bug is expected to be closed. This depends on the severity of the bug. Actual Date of Closure: As the name suggests, actual date of closure of the bug i.e. date at which the bug was fixed and retested successfully. Priority: Priority of the bug fixing. This specifically depends upon the functionality that it is hindering. Generally Medium, Low, High, Urgent are the type of severity that are used. Severity: This is typically a numerical field, which displays the severity of the bug. It can range from 1 to 5, where 1 is high severity and 5 is the lowest. Status: This field displays current status of the bug. A status of ‘New’ is automatically assigned to a bug when it is first time reported by the tester, further the status is changed to Assigned, Open, Retest, Pending Retest, Pending Reject, Rejected, Closed, Postponed, Deferred etc. as per the progress of bug fixing process. Bug ID: This is a unique ID i.e. number created for the bug at the time of reporting, which identifies the bug uniquely. Attachment: Sometimes it is necessary to attach screen-shots for the tested functionality that can help tester in explaining the testing he had done and it also helps developers in re-creating the similar testing condition. Test Case Failed: This field contains the test case that is failed for the bug. Any of above given fields can be made mandatory, in which the tester has to enter a valid data at the time of reporting a bug. Making a field mandatory or optional depends on the company requirements and can take place at any point of time in a Software Testing project.
What needs to be done if I find a bug/error?
In normal terms, if a bug or error is detected in a system, it needs to be communicated to the developer in order to get it fixed. Right from the first time any bug is detected till the point when the bug is fixed and closed, it is assigned various statuses which are New, Open, Retest, Reject, Deferred, and Closed. Write all the Defect Status that you worked on.
Statuses associated with a bug:
New: When a bug is found/revealed for the first time, the software tester communicates it to his/her team leader (Test Leader) in order to confirm if that is a valid bug. After getting confirmation from the Test Lead, the software tester logs the bug and the status of ‘New’ is assigned to the bug. Assigned: After the bug is reported as ‘New’, it comes to the Development Team. The development team verifies if the bug is valid. If the bug is valid, development leader assigns it to a developer to fix it and a status of ‘Assigned’ is assigned to it. Open: Once the developer starts working on the bug, he/she works the bug with the status ‘Open’ to indicate that he/she is working on it to find a solution. Fixed: Once the developer makes necessary changes in the code and verifies the code, he/she marks the bug as ‘Fixed’ and passes it over to the Development Lead in order to pass it to the Testing team. Fixed Ready for Retest:
After the bug is fixed, it is passed back to the testing team to get retested and the status of ‘Fixed-Ready for Retest’ is assigned to it.
Testing Passed: The tester retests the bug and if the problem solves, the tester sends the defect to Test Lead by changing the status ‘Retest Passed’.
Testing Failed: The tester retests the bug and if the same problem persists, the tester sends the defect to Test Lead by changing the status ‘Retest Failed’.Closed: After the bug is assigned a status of ‘Fixed Ready for Retest’, it is again tested. If the problem is solved, the tester closes it and marks it with ‘Closed’ status.
Reopen: If after retesting the software for the bug opened, if the system behaves in the same way or same bug arises once again, then the tester reopens the bug and again sends it back to the developer marking its status as ‘Reopen’. Rejected: If the Testing Leader finds that the system is working according to the specifications or the bug is invalid as per the explanation from the development, he/she rejects the bug and marks its status as ‘Rejected’. Deferred: In some cases a particular bug stands no importance and is needed to be/can be avoided, that time it is marked with ‘Deferred’ status.
As we already have discussed importance of Software Testing in any software development project (Just to summarize: Software testing helps in improving quality of software and deliver a cost effective solution which meet customer requirements), it becomes necessary to log a defect in a proper way, track the defect, and keep a log of defects for future reference etc. As a tester tests an application and if he/she finds any defect, the life cycle of the defect starts and it becomes very important to communicate the defect to the developers in order to get it fixed, keep track of current status of the defect, find out if any such defect (similar defect) was ever found in last attempts of testing etc. For this purpose, previously manually created documents were used, which were circulated to everyone associated with the software project (developers and testers), now a days many Bug Reporting Tools are available, which help in tracking and managing bugs in an effective way. How to report a bug? It’s a good practice to take screen shots of execution of every step during software testing.
If any test case fails during execution of a test case in the Test Lab section of Test Director, it needs to be failed in the bug-reporting tool (Test Director) and a bug has to be reported/logged for the same.
The Tester clicks on the Add Defects icon, a dialog box displays.
Then in the dialog box, all the mandatory fields from the contents of bug (such as Project, Summary, Description, Status, Detected By, Assigned To, Date Detected, Detected in Version, Closed in Version, Expected Date of Closure, Actual Date of Closure, Severity, Priority and Bug ID etc.) are filled and steps to reproduce the bug, detailed description of the bug is given along with the expected and actual results. The screen-shots taken at the time of execution of test case are attached to the bug for reference by the developer.
Tester clicks on the Submit button, then a unique Bug ID is generated for the reported bug automatically, which is then associated with the failed test case. This Bug ID helps in associating the bug with the failed test case. After the bug is reported, it is assigned a status of ‘New’, which goes on changing as the bug fixing process progresses. If more than one tester are testing the software application, it becomes a possibility that some other tester might already have reported a bug for the same defect found in the application. In such situation, it becomes very important for the tester to find out if any bug has been reported for similar type of defect. If yes, then the test case has to be blocked with the previously raised bug (in this case, the test case has to be executed once the bug is fixed). And if there is no such bug reported previously, the tester can report a new bug and fail the test case for the newly raised bug. If no bug-reporting tool is used, then in that case, the test case is written in a tabular manner in a file with four columns containing Test Step No, Test Step Description, Expected Result and Actual Result. The expected and actual results are written for each step and the test case is failed for the step at which the test case fails. This file containing test case and the screen shots taken are sent to the developers for reference. As the tracking process is not automated, it becomes important keep updated information of the bug that was raised till the time it is closed.
What is a bug/error/defect/flaw?
A bug in software product is any exception that can hinder the functionality of either the whole software or part of it. How do I find out a BUG/ERROR?
Basically, test cases/scripts are run in order to find out any unexpected behavior of the software product under test. If any such unexpected behavior or exception occurs, it is called as a bug. What is a Test Case?
A test case is a noted/documented set of steps/activities that are carried out or executed on the software in order to confirm its functionality/behavior to certain set of inputs.
What is a TestDirector?
It is a web based test management tool that acts as a repository of requirements, defects, test, test cases, test scripts, and analyzes the results.
How many components or tabs are there?
There are 4 phases in TD: Requirement, Test Plan, Test Lab, and Defects.
Describe what you do with all the tabs?
In Requirement phase, one has to import all the necessary specification, data, information, functionalities that an application must pass in order to market the product.
In the Test Plan phase, we focus on the design of it. We write all the necessary test cases.
In the Test Lab phase, we test all the test cases, analyze them, and decide if they pass or fail depending on the requirements.
Finally in the Defect phase, we analyze and then document the severity/priority of the defects found.
What is Requirement Tracability/Coverage?
It is the linking between requirements and tests.
What is the difference between Severity and Priority?
Severity is how dangerous, effect-wise, a defect is and priority is how soon, time-wise, that defect needs to be fixed.
Write all Severity levels.
· 1-Unable to use the application
· 2-Serious defect but there is a work around
· 3-Minor defect with a work around
4-Cosmetic
Write all Priority levels.
· 1- Low
· 2-Medium
· 3-High
· 4-Urgent
What is Reproducible?
A function will not work if we are able to regenerate the same defect by trying the requirement test again is reproducible.
What is Filtering?
Filtering is used to check how may defects someone has assigned; or when, or to whom and so on.
How do you generate reports and graphs in TD?
After the last or defect phase is completed, if we click the “Analysis” tab, we will see both reports and graphing options.
What is a Template?
A template is any common steps, tabs, functions, interface, structures that can be re-used.
How do you create a template?
One would create a template in the tree view of our test; where if we right click on the specific/common requirements, we see the option “create template”.
What happens when you do not do Requirement Coverage?
If we don’t do Requirement Coverage, once a test case fails in the test lab, we will not be able to see the corresponding requirement as failed in the requirement tab.
What is the difference between Test Case and Test Script?
Test case is the manually written/designed test cases.
And Test script is the automated design script.
How do you change your login password in TD?
After starting the TD Application, we would click on the “Tool” menu on top and find in the list “Change Password”; then we just follow direction and type old password, new password and again new password. Then click ok and we are done.
What do you call the window testdirector-testlab?
"Execution Grid". It is place from where we Run all Manual / Automated Scripts.
How do you create new test sets in TD?
Login to TD.
Click on "Test Lab" tab.
QuickTest Professional (QTP)
Click to read WinRunner or Back to Top
Click to read LoadRunner
Click to read QalityCenter
Click to read Quick_Test_Pro
Click to read SampleQuestions
What is QTP?
It is a functional and regression testing software that tests both web-based and windows applications.
Describe all recording modes?
There are 3 Recording modes. They are Normal Mode, Low Level Mode, and Analog Mode. QTP uses Normal Mode by default, which records almost anything. Low Level recording is used when there is any recognition problem using the other methods, which forces recognition. Analog Mode is the recognition of keyboard inputs, mouse clicks, and signatures.
What is the difference between Manual and Automated test?
Manual testing is time consuming, not robust, uses human resources, inconsistent, harder to repeat a test and costly.
Automated testing is faster, robust, easily repeatable, reusable and cost efficient.
What is an Object Repository?
It’s a data storage that keeps a back up of all the objects used in an application. It acts as a translator between the Script and Application Under Test (AUT) because it knows both the logical name and the properties of an object.
What is add-in? Which add-in did you work with?
Add-in helps an application to recognize unique objects, object properties, programming languages. It’s also known as plug-ins. I’ve worked with Web, ActiveX, Java Plug-in, Multimedia and Visual Basic add-in.
Write the syntax when you record in Analog recording mode?
Desktop.RunAnalog “Track1” or
Window(“Microsoft Internet”).RunAnalog “Track2”
Write the syntax when you record in Low Level recording mode?
Windows(“Microsoft Internet Explorer”).WinObject(“Internet Explorer_Server”).Type “jojo”
Write the syntax when you record in Normal recording mode?
Browser(“Welcome: Mercury”).Page(“Find a Flight:”).WebList(“fromPort”).select “New York”
What is a Checkpoint? Define all the Checkpoints in QTP?
Checkpoints are used to verify that the expected value/result matches the exact value/result. Following are some examples:
Standard: Checks values of an object’s properties; it checks that a radio button is selected.
Image: Checks the property values of an image; it checks that the image source file is correct.
Table: Checks information in a table; it checks that the value in a table cell is correct.
Page: Checks the characteristics of a Web page; it checks how long a Web page takes to load or if a Web page contains broken links.
Text / Text Area: It checks whether the expected text string is displayed in the expected location on a Web page or dialog box.
Bitmap: It checks that a Web page (or any portion of it) is displayed as expected.
Database: Checks the contents of databases accessed by an application or Web site; it checks that the value in a database query is correct.
Accessibility: Identifies areas of a Web site to check if the images on a Web page include ALT properties, required by the W3C Web Content Accessibility Guidelines.
XML: Checks the data content of XML documents.
Explain the checkpoints in QTP.
A checkpoint verifies that expected information is displayed in a Application while the test is running. You can add eight types of checkpoints to your test for standard web objects using QTP.
A page checkpoint checks the characteristics of a Application
A text checkpoint checks that a text string is displayed in the appropriate place on a Application.
An object checkpoint (Standard) checks the values of an object on a Application.
An image checkpoint checks the values of an image on a Application.
A table checkpoint checks information within a table on a Application
An Accessibility checkpoint checks the web page for Section 508 compliance.
An XML checkpoint checks the contents of individual XML data files or XML documents that are part of your Web application.
A database checkpoint checks the contents of databases accessed by your web site.
What is the syntax of a Checkpoint?
Browser(“Welcome: Mercury”).Page(“Book a Flight:”).Checkpoint(“Book a Flight”)
What is Parameterization?
It is the reusability of the same code for different sets of data.
How many types of parameters are there? Define Input Value or Output Value?
There is Input Parameterization, which is data that is entered manually before executing tests.
There is Output Parameterization, which is data that is retrieved dynamically from a database during or after the execution of test.
Define Regular Expression. Give some example.
Regular Expression is a string that specifies a complex search phrase. For example, (.), (*), (^), ([]), and (+).
What is a Modular test? Why do you need Modular testing?
Modular test is dividing a test into several actions that can be re-used or edited or called by several other tests, which is also known as code re-usability.
What is the difference between Call to Action and Copy to Action?
A call to action cannot be modified at the called test, but only in its original test; whereas copy to action can, which creates a duplicate of an action.
What is Synchronization? Write the statement/syntax for Synchronization?
Synchronization is waiting for one object to finish its action to go to the next object.
Syntax: Window(“Flight Reservation”).WinButton(“Update Order”). WaitProperty ”enabled”, 1, 3000
What is the purpose of Recovery Scenarios?
Sometimes there are errors during a recording session that can QTP can recover using Recovery Scenarios and continue running the test. It works as an Object Repository that backup objects and its properties for such events.
What is an Optional Step?
This is used to block unnecessary pop up box, warnings, and messages that can interfere with running any tests for error.
Define Virtual Objects.
Virtual Object allows us to record and run tests on objects that are not normally recognized by QTP.
Why do you need to enable Object Smart Identification?
QTP by default records any objects’ distinct properties but even after distinct properties, an object may have duplication or be repeated; therefore by enabling the Smart Identification it uses auxilliary/subsidiary properties to identify other distinct features. Otherwise, Ordinal position is use to make the distinction by the distance of two objects.
What is the purpose of doing Descriptive programming?
Descriptive programming is used to bypass the use of Object repository, which knows the logical name and the properties of an object. In this case Object spy is used to gather the properties of an object and then hand code the properties in the script.
What are windows API functions?
Application Programming Interface (API) is a software interface used by other programs to read or write data from disk, gather file attributes, and change a color on dialog boxes.
It is also a collection of code hidden inside dynamic link library files.
What is User-Defined function?
It is codes manually writing for different functions for reusability in one or multiple tests.
For example, if you have a large segments of code that you need to use several times in one or different tests, you would create a user-defined function in order to make your tests easier to design and to read.
What is the difference between Tree View/Expert View?
In Expert View we see our recorded steps in Visual Basic code language; whereas, in Tree View, we see the same-recorded steps in a normal English language view.
What is the difference between Design Time/Runtime data table?
The Design-Time data table reflects data prior to the execution of the script.
The Runtime data table represents the table as it looks at the completion of script execution.
What is a data driven test?
Data driven test uses input parameters to play back the test using different values of input data.
What is the file extension of the code file & object repository file in QTP?
Object Repository is like GUIMAP in winrunner. It learns the description of Objects logical name and the physical description. It contains two files, per Action and Shared.. File extension for per action is (.mtr) and the shared is (.tsr). Per action for each test , it creates a file and shared creates one file for the entite application ... for code file the extension is .vbs
Explain the concept of object repository & how QTP recognizes objects.
Object Repository: displays a tree of all objects in the current component or in the current action or entire test (depending on the object repository mode you selected). We can view or modify the test object description of any test object in the repository or to add new objects to the repository. Quickest learns the default property values and determines in which test object class it fits. If it is not enough it adds assistive properties, one by one to the description until it has compiled the unique description. If no assistive properties are available, then it adds a special Ordinal identifier such as objects location on the page or in the source code.
When you create test, all the information about the objects in your test is stored in object repository. There are two types of object Repositories:
1. Shared object repository 2. Per action repository
What are the properties you would use for identifying a browser & page when using descriptive programming?
Title is the property we use.ex: Browser ("Title:="xxx").page("Title:="xxxx").....
"name" would be another property apart from "title" that we can use. ex: Browser("name:="xxx"").page("name:="xxxx"")..... OR We can also use the property "micClass". ex: Browser("micClass:=browser").page("micClass:=page")....
For Browser : Name
For Page : Title
What are the different scripting languages you could use when working with QTP ?
You can’t use JScript in QTP.
You can run your java script (.js) and vbscript (.vbs) using Windows Script Host engine. So its not related to running JScript in QTP. You can only run VBScript in QTP.
Give me an example where you have used a COM interface in your QTP project.
com inteface appears in the scenario of front end and back end.for eg:if you r using oracle as back end and front end as VB or any language then for better compatibility we will go for an interface.of which COM wil be one among those intefaces.
Few basic questions on commonly used Excel VBA functions.
Common functions are: Coloring the cell Auto fit cell setting navigation from link in one cell to other saving
Explain the keyword create object with an example.
Creates and returns a reference to an Automation object
Syntax: CreateObject(servername.typename [, location]) Arguments servername:Required. The name of the application providing the object. typename : Required. The type or class of the object to create. location : Optional. The name of the network server where the object is to be created.
create object creates handle to the instance of the specified object so that we program can use the methods on the specified object. It is used for implementing Automation (as defined by microsoft). ex: set oDesc= createobject(Excel.application) odesc.activeworksheet=1
*
Createobject:Creates and returns a reference to an Automation object.Example:Dim ExcelSheetSet ExcelSheet = CreateObject("Excel.Sheet")
Explain in brief about the QTP Automation Object Model.
Essentially all configuration and run functionality provided via the QuickTest interface is in some way represented in the QuickTest automation object model via objects, methods, and properties. Although a one-on-one comparison cannot always be made, most dialog boxes in QuickTest have a corresponding automation object, most options in dialog boxes can be set and/or retrieved using the corresponding object property, and most menu commands and other operations have corresponding automation methods. You can use the objects, methods, and properties exposed by the QuickTest automation object model, along with standard programming elements such as loops and conditional statements to design your program.
How Does Run time data (Parameterization) is handled in QTP?
You can then enter test data into the Data Table, an integrated spreadsheet with the full functionality of Excel, to manipulate data sets and create multiple test iterations, without programming, to expand test case coverage. Data can be typed in or imported from databases, spreadsheets, or text files.
What is keyword view and Expert view in QTP?
QuickTest’s Keyword Driven approach, test automation experts have full access to the underlying test and object properties, via an integrated scripting and debugging environment that is round-trip synchronized with the Keyword View.
Advanced testers can view and edit their tests in the Expert View, which reveals the underlying industry-standard VBScript that
QuickTest Professional automatically generates. Any changes made in the Expert View are automatically synchronized with the
Keyword View.
Explain about the Test Fusion Report of QTP.
Once a tester has run a test, a TestFusion report displays all aspects of the test run: a high-level results overview, an expandable Tree View of the test specifying exactly where application failures occurred, the test data used, application screen shots for every step that highlight any discrepancies, and detailed explanations of each checkpoint pass and failure. By combining TestFusion reports with QuickTest Professional, you can share reports across an entire QA and development team.
To which environments does QTP supports?
QuickTest Professional supports functional testing of all enterprise environments, including Windows, Web, ..NET, Java/J2EE, SAP,Siebel, Oracle, PeopleSoft, Visual Basic, ActiveX, mainframe terminal emulators, and Web services.
What is QTP ?
QuickTest is a graphical interface record-playback automation tool. It is able to work with any web, java or windows client application. Quick Test enables you to test standard web objects and ActiveX controls. In addition to these environments, QuickTest Professional also enables you to test Java applets and applications and multimedia objects on Applications as well as standard Windows applications, Visual Basic 6 applications and .NET framework applications...
Explain QTP Testing process.
The QuickTest testing process consists of 6 main phases:
Create your test plan
Prior to automating there should be a detailed description of the test including the exact steps to follow, data to be input, and all items to be verified by the test. The verification information should include both data validations and existence or state verifications of objects in the application.
Recording a session on your application
As you navigate through your application, QuickTest graphically displays each step you perform in the form of a collapsible icon-based test tree. A step is any user action that causes or makes a change in your site, such as clicking a link or image, or entering data in a form.
Enhancing your test
Inserting checkpoints into your test lets you search for a specific value of a page, object or text string, which helps you identify whether or not your application is functioning correctly.
NOTE: Checkpoints can be added to a test as you record it or after the fact via the Active Screen. It is much easier and faster to add the checkpoints during the recording process.
Broadening the scope of your test by replacing fixed values with parameters lets you check how your application performs the same operations with multiple sets of data.
Adding logic and conditional statements to your test enables you to add sophisticated checks to your test.
Debugging your test
If changes were made to the script, you need to debug it to check that it operates smoothly and without interruption.
Running your test on a new version of your application
You run a test to check the behavior of your application. While running, QuickTest connects to your application and performs each step in your test.
Analyzing the test results
You examine the test results to pinpoint defects in your application.
Reporting defects
As you encounter failures in the application when analyzing test results, you will create defect reports in Defect Reporting Tool.
Explain the QTP Tool interface.
It contains the following key elements:
Title bar, displaying the name of the currently open test Menu bar, displaying menus of QuickTest commands
File toolbar, containing buttons to assist you in managing tests.
Test toolbar, containing buttons used while creating and maintaining tests.Debug toolbar, containing buttons used while debugging tests. Note: The Debug toolbar is not displayed when you open QuickTest for the first time. You can display the Debug toolbar by choosing View > Toolbars > Debug. Note that this tutorial does not describe how to debug a test. For additional information, refer to the QuickTest Professional User's Guide.
Action toolbar, containing buttons and a list of actions, enabling you to view the details of an individual action or the entire test flow. Note: The Action toolbar is not displayed when you open QuickTest for the first time. You can display the Action toolbar by choosing View > Toolbars > Action. If you insert a reusable or external action in a test, the Action toolbar is displayed automatically. For additional information, refer to the QuickTest Professional User's Guide.
Test pane, containing two tabs to view your test-the Tree View and the Expert View
Test Details pane, containing the Active Screen
Data Table, containing two tabs, Global and Action, to assist you in parameterizing your test
Debug Viewer pane, containing three tabs to assist you in debugging your test-Watch Expressions, Variables, and Command. (The Debug Viewer pane can be opened only when a test run pauses at a breakpoint.)
Status bar, displaying the status of the test
How QTP recognizes Objects in AUT?
QuickTest stores the definitions for application objects in a file called the Object Repository. As you record your test, QuickTest will add an entry for each item you interact with. Each Object Repository entry will be identified by a logical name (determined automatically by QuickTest), and will contain a set of properties (type, name, etc) that uniquely identify each object.
Each line in the QuickTest script will contain a reference to the object that you interacted with, a call to the appropriate method (set, click, check) and any parameters for that method (such as the value for a call to the set method). The references to objects in the script will all be identified by the logical name, rather than any physical, descriptive properties.
What are the types of Object Repository in QTP?
QuickTest has two types of object repositories for storing object information: shared object repositories and action object repositories. You can choose which type of object repository you want to use as the default type for new tests, and you can change the default as necessary for each new test.
The object repository per-action mode is the default setting. In this mode, QuickTest automatically creates an object repository file for each action in your test so that you can create and run tests without creating, choosing, or modifying object repository files. However, if you do modify values in an action object repository, your changes do not have any effect on other actions. Therefore, if the same test object exists in more than one action and you modify an object's property values in one action, you may need to make the same change in every action (and any test) containing the object.
In how many ways we can add checkpoints to an application using QTP?
We can add checkpoints while recording the application or we can add after recording is completed using Active screen (Note: To perform the second one The Active screen must be enabled while recording).
How does QTP identify the object in the application?
QTP identifies the object in the application by LogicalName and Class.
For example :
The Edit box is identified by
Logical Name : PSOPTIONS_BSE_TIME20
Class: WebEdit
If an application name is changes frequently i.e while recording it has name “Window1” and then while running its “Windows2” in this case how does QTP handles?
QTP handles those situations using “Regular Expressions”.
What is parameterize Tests?
When you test your application, you may want to check how it performs the same operations with multiple sets of data. For example, suppose you want to check how your application responds to ten separate sets of data. You could record ten separate tests, each with its own set of data. Alternatively, you can create a parameterized test that runs ten times: each time the test runs, it uses a different set of data.
What is test object model in QTP?
The test object model is a large set of object types or classes that QuickTest uses to represent the objects in your application. Each test object class has a list of properties that can uniquely identify objects of that class and a set of relevant methods that QuickTest can record for it.
A test object is an object that QuickTest creates in the test or component to represent the actual object in your application. QuickTest stores information about the object that will help it identify and check the object during the
run session.
A run-time object is the actual object in your Web site or application on which methods are performed during the run session.
When you perform an operation on your application while recording, QuickTest:
➤ identifies the QuickTest test object class that represents the object on which you performed the operation and creates the appropriate test object
➤ reads the current value of the object’s properties in your application and stores the list of properties and values with the test object
➤ chooses a unique name for the object, generally using the value of one of its prominent properties
➤ records the operation that you performed on the object using the appropriate QuickTest test object method
For example, suppose you click on a Find button with the following HTML source code:
QuickTest identifies the object that you clicked as a WebButton test object.It creates a WebButton object with the name Find, and records the following properties and values for the Find WebButton:
It also records that you performed a Click method on the WebButton.
QuickTest displays your step in the Keyword View like this:
QuickTest displays your step in the Expert View like this:
Browser("Mercury Interactive").Page("Mercury Interactive").
WebButton("Find").Click
What is Object Spy in QTP?
Using the Object Spy, you can view the properties of any object in an open application. You use the Object Spy pointer to point to an object. The Object Spy displays the selected object’s hierarchy tree and its properties and values in the Properties tab of the Object Spy dialog box.
What is the Diff between Image checkpoint and Bit map Checkpoint?
Image checkpoints enable you to check the properties of a Web image. You can check an area of a Web page or application as a bitmap. While creating a test or component, you specify the area you want to check by selecting an object. You can check an entire object or any area within an object. QuickTest captures the specified object as a bitmap, and inserts a checkpoint in the test or component. You can also choose to save only the selected area of the object with your test or component in order to save disk Space For example, suppose you have a Web site that can display a map of a city the user specifies. The map has control keys for zooming. You can record the new map that is displayed after one click on the control key that zooms in the map. Using the bitmap checkpoint, you can check that the map zooms in correctly.
You can create bitmap checkpoints for all supported testing environments (as long as the appropriate add-ins are loaded).
Note: The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.
How many ways we can parameterize data in QTP?
There are four types of parameters:
Test, action or component parameters enable you to use values passed from your test or component, or values from other actions in your test.
Data Table parameters enable you to create a data-driven test (or action) that runs several times using the data you supply. In each repetition, or iteration, QuickTest uses a different value from the Data Table.
Environment variable parameters enable you to use variable values from other sources during the run session. These may be values you supply, or values that QuickTest generates for you based on conditions and options you choose.
Random number parameters enable you to insert random numbers as values in your test or component. For example, to check how your application handles small and large ticket orders, you can have QuickTest generate a random number and insert it in a number of tickets edit field.
How do you do batch testing in WR & is it possible to do in QTP, if so explain?
Batch Testing in WR is nothing but running the whole test set by selecting "Run Testset" from the "Execution Grid".The same is possible with QTP also. If our test cases are automated then by selecting "Run Testset" all the test scripts can be executed. In this process the Scripts get executed one by one by keeping all the remaining scripts in "Waiting" mode.
If I give some thousand tests to execute in 2 days what do you do?
Adhoc testing is done. It Covers the least basic functionalities to verify that the system is working fine.
What does it mean when a checkpoint is in red color? What do you do?
A red color indicates failure. Here we analyze the cause for failure whether it is a Script Issue or Environment Issue or an Application issue.
Test Automation: 1. What automating testing tools are you familiar with? 2. How did you use automating testing tools in your job? 3. Describe some problem that you had with automating testing tool. 4. How do you plan test automation? 5. Can test automation improve test effectiveness? 6. What is data - driven automation? 7. What are the main attributes of test automation? 8. Does automation replace manual testing? 9. How will you choose a tool for test automation? 10. How you will evaluate the tool for test automation? 11. What are main benefits of test automation? 12. What could go wrong with test automation? 13. How you will describe testing activities? 14. What testing activities you may want to automate? 15. Describe common problems of test automation. 16. What types of scripting techniques for test automation do you know? 17. What are principles of good testing scripts for automation? 18. What tools are available for support of testing during software development life cycle? 19. Can the activities of test case design be automated? 20. What are the limitations of automating software testing? 21. What skills needed to be a good test automator? 22. How to find that tools work well with your existing system? 23.Describe some problem that you had with automating testing tool. 24.What are the main attributes of test automation? 25.What testing activities you may want to automate in a project? 26.How to find that tools work well with your existing system?
Load Testing: 1.What criteria would you use to select Web transactions for load testing?2.For what purpose are virtual users created?3.Why it is recommended to add verification checks to your all your scenarios?4.In what situation would you want to parameterize a text verification check?5.Why do you need to parameterize fields in your virtual user script?6.What are the reasons why parameterization is necessary when load testing the Web server and the database server?7.How can data caching have a negative effect on load testing results?8.What usually indicates that your virtual user script has dynamic data that is dependent on you parameterized fields?9.What are the benefits of creating multiple actions within any virtual user script?
General questions: 1. What types of documents would you need for QA, QC, and Testing? 2. What did you include in a test plan? 3. Describe any bug you remember. 4. What is the purpose of the testing? 5. What do you like (not like) in this job? 6. What is quality assurance? 7. What is the difference between QA and testing? 8. How do you scope, organize, and execute a test project? 9. What is the role of QA in a development project? 10. What is the role of QA in a company that produces software? 11. Define quality for me as you understand it 12. Describe to me the difference between validation and verification. 13. Describe to me what you see as a process. Not a particular process, just the basics of having a process. 14. Describe to me when you would consider employing a failure mode and effect analysis. 15. Describe to me the Software Development Life Cycle as you would define it. 16. What are the properties of a good requirement? 17. How do you differentiate the roles of Quality Assurance Manager and Project Manager? 18. Tell me about any quality efforts you have overseen or implemented. Describe some of the challenges you faced and how you overcame them. 19. How do you deal with environments that are hostile to quality change efforts? 20. In general, how do you see automation fitting into the overall process of testing? 21. How do you promote the concept of phase containment and defect prevention? 22. If you come onboard, give me a general idea of what your first overall tasks will be as far as starting a quality effort. 23. What kinds of testing have you done? 24. Have you ever created a test plan? 25. Have you ever written test cases or did you just execute those written by others? 26. What did your base your test cases? 27. How do you determine what to test? 28. How do you decide when you have 'tested enough?' 29. How do you test if you have minimal or no documentation about the product? 30. Describe me to the basic elements you put in a defect report? 31. How do you perform regression testing? 32. At what stage of the life cycle does testing begin in your opinion? 33. How do you analyze your test results? What metrics do you try to provide? 34. Realising you won't be able to test everything - how do you decide what to test first? 35. Where do you get your expected results? 36. If automating - what is your process for determining what to automate and in what order? 37. In the past, I have been asked to verbally start mapping out a test plan for a common situation, such as an ATM. The interviewer might say, "Just thinking out loud, if you were tasked to test an ATM, what items might you test plan include?" These type questions are not meant to be answered conclusively, but it is a good way for the interviewer to see how you approach the task. 38. If you're given a program that will average student grades, what kinds of inputs would you use? 39. Tell me about the best bug you ever found. 40. What made you pick testing over another career? 41. What is the exact difference between Integration & System testing, give me examples with your project. 42. How did you go about testing a project? 43. When should testing start in a project? Why? 44. How do you go about testing a web application? 45. Difference between Black & White box testing 46. What is Configuration management? Tools used? 47. What do you plan to become after say 2-5yrs (Ex: QA Manager, Why?) 48. Would you like to work in a team or alone, why? 49. Give me 5 strong & weak points of yours 50. Why do you want to join our company? 51. When should testing be stopped? 52. What sort of things would you put down in a bug report? 53. Who in the company is responsible for Quality? 54. Who defines quality? 55. What is an equivalence class? 56. Is a "A fast database retrieval rate" a testable requirement? 57. Should we test every possible combination/scenario for a program? 58. What criteria do you use when determining when to automate a test or leave it manual? 59. When do you start developing your automation tests? 60. Discuss what test metrics you feel are important to publish an organization? 61. In case anybody cares, here are the questions that I will be asking: 62. Describe the role that QA plays in the software lifecycle. 63. What should Development require of QA? 64. What should QA require of Development? 65. How would you define a "bug?" 66. Give me an example of the best and worst experiences you've had with QA. 67. How does unit testing play a role in the development / software lifecycle? 68. Explain some techniques for developing software components with respect to testability. 69. Describe a past experience with implementing a test harness in the development of software. 70. Have you ever worked with QA in developing test tools? Explain the participation Development should have with QA in leveraging such test tools for QA use. 71. Give me some examples of how you have participated in Integration Testing. 72. How would you describe the involvement you have had with the bug-fix cycle between Development and QA? 72. What is unit testing? 73. Describe your personal software development process. 74. How do you know when your code has met specifications? 75. How do you know your code has met specifications when there are no specifications? 76. Describe your experiences with code analyzers. 77. How do you feel about cyclomatic complexity? 78. Who should test your code? 79.How do you survive chaos? 80. What processes/methodologies are you familiar with? 81. What type of documents would you need for QA/QC/Testing? 82. How can you use technology to solve problem? 83. What type of metrics would you use? 84. How to find that tools work well with your existing system? 85. What automated tools are you familiar with? 86. How well you work with a team? 87. How would you ensure 100% coverage of testing? 88. How would you build a test team? 89. What problem you have right now or in the past? How you solved it? 90. What you will do during the first day of job? 91. What would you like to do five years from now? 92. Tell me about the worst boss you've ever had. 93. What are your greatest weaknesses? 94. What are your strengths? 95. What is a successful product? 96. What do you like about Windows? 97. What is good code? 98. Who is Kent Beck, Dr Grace Hopper, Dennis Ritchie? 99. What are basic, core, practises for a QA specialist? 100. What do you like about QA? 101. What has not worked well in your previous QA experience and what would you change? 102. How you will begin to improve the QA process? 103. What is the difference between QA and QC? 104. What is UML and how to use it for testing? 105. What is CMM and CMMI? What is the difference? 106. What do you like about computers? 107. Do you have a favourite QA book? More than one? Which ones? And why. 108. What is the responsibility of programmers vs QA? 109.What are the properties of a good requirement? 110.Ho to do test if we have minimal or no documentation about the product? 111.What are all the basic elements in a defect report? 112.Is an "A fast database retrieval rate" a testable requirement?
1. What is software quality assurance? 2. What is the value of a testing group? How do you justify your work and budget? 3. What is the role of the test group vis-à¶is documentation, tech support, and so forth? 4. How much interaction with users should testers have, and why? 5. How should you learn about problems discovered in the field, and what should you learn from those problems? 6. What are the roles of glass-box and black-box testing tools? 7. What issues come up in test automation, and how do you manage them? 8. What development model should programmers and the test group use? 9. How do you get programmers to build testability support into their code? 10. What is the role of a bug tracking system? 11. What are the key challenges of testing? 12. Have you ever completely tested any part of a product? How? 13. Have you done exploratory or specification-driven testing? 14. Should every business test its software the same way? 15. Discuss the economics of automation and the role of metrics in testing. 16. Describe components of a typical test plan, such as tools for interactive products and for database products, as well as cause-and-effect graphs and data-flow diagrams. 17. When have you had to focus on data integrity? 18. What are some of the typical bugs you encountered in your last assignment? 19. How do you prioritize testing tasks within a project? 20. How do you develop a test plan and schedule? Describe bottom-up and top-down approaches. 21. When should you begin test planning? 22. When should you begin testing? 23. Do you know of metrics that help you estimate the size of the testing effort? 24. How do you scope out the size of the testing effort? 25. How many hours a week should a tester work? 26. How should your staff be managed? How about your overtime? 27. How do you estimate staff requirements? 28. What do you do (with the project tasks) when the schedule fails? 29. How do you handle conflict with programmers? 30. How do you know when the product is tested well enough? 31. What characteristics would you seek in a candidate for test-group manager? 32. What do you think the role of test-group manager should be? Relative to senior management? Relative to other technical groups in the company? Relative to your staff? 33. How do your characteristics compare to the profile of the ideal manager that you just described? 34. How does your preferred work style work with the ideal test-manager role that you just described? What is different between the way you work and the role you described? 35. Who should you hire in a testing group and why? 36. What is the role of metrics in comparing staff performance in human resources management? 37. How do you estimate staff requirements? 38. What do you do (with the project staff) when the schedule fails? 39. Describe some staff conflicts you’ve handled.
1. Why did you ever become involved in QA/testing?
2. What is the testing lifecycle and explain each of its phases?
3. What is the difference between testing and Quality Assurance?
4. What is Negative testing?
5. What was a problem you had in your previous assignment (testing if possible)? How did you resolve it?
6. What are two of your strengths that you will bring to our QA/testing team?
7. How would you define Quality Assurance?
8. What do you like most about Quality Assurance/Testing?
9. What do you like least about Quality Assurance/Testing?
10. What is the Waterfall Development Method and do you agree with all the steps?
11. What is the V-Model Development Method and do you agree with this model?
12. What is the Capability Maturity Model (CMM)? At what CMM level were the last few companies you worked?
13. What is a "Good Tester"?
14. Could you tell me two things you did in your previous assignment (QA/Testing related hopefully) that you are proud of?
15. List 5 words that best describe your strengths.
16. What are two of your weaknesses?
17. What methodologies have you used to develop test cases?
18. In an application currently in production, one module of code is being modified. Is it necessary to re- test the whole application or is it enough to just test functionality associated with that module?
19. Define each of the following and explain how each relates to the other: Unit, System, and Integration testing.
20. Define Verification and Validation. Explain the differences between the two.
21. Explain the differences between White-box, Gray-box, and Black-box testing.
22. How do you go about going into a new organization? How do you assimilate?
23. Define the following and explain their usefulness: Change Management, Configuration Management, Version Control, and Defect Tracking.
24. What is ISO 9000? Have you ever been in an ISO shop?
25. When are you done testing?
26. What is the difference between a test strategy and a test plan?
27. What is ISO 9003? Why is it important
28. What are ISO standards? Why are they important?
29. What is IEEE 829? (This standard is important for Software Test Documentation-Why?)
30. What is IEEE? Why is it important?
31. Do you support automated testing? Why?
32. We have a testing assignment that is time-driven. Do you think automated tests are the best solution?
33. What is your experience with change control? Our development team has only 10 members. Do you think managing change is such a big deal for us?
34. Are reusable test cases a big plus of automated testing and explain why.
35. Can you build a good audit trail using Compuware's QACenter products. Explain why.
36. How important is Change Management in today's computing environments?
37. Do you think tools are required for managing change. Explain and please list some tools/practices which can help you managing change.
38. We believe in ad-hoc software processes for projects. Do you agree with this? Please explain your answer.
39. When is a good time for system testing?
40. Are regression tests required or do you feel there is a better use for resources?
41. Our software designers use UML for modeling applications. Based on their use cases, we would like to plan a test strategy. Do you agree with this approach or would this mean more effort for the testers.
42. Tell me about a difficult time you had at work and how you worked through it.
43. Give me an example of something you tried at work but did not work out so you had to go at things another way.
44. How can one file compare future dated output files from a program which has change, against the baseline run which used current date for input. The client does not want to mask dates on the output files to allow compares. - Answer-Rerun baseline and future date input files same # of days as future dated run of program with change. Now run a file compare against the baseline future dated output and the changed programs' future dated output.
Interviewing Suggestions
If you do not recognize a term ask for further definition. You may know the methodology/term but you have used a different name for it.
Always keep in mind that the employer wants to know what you are going to do for them, with that you should always stay/be positive.
Interview Questions
What is the structure of the company?
Who is going to do the interview-possible background information of interviewer?
What is the employer's environment (platforms, tools, etc.)?
What are the employer's methods and processes used in software arena?
What is the employer's philosophy?
What is the project all about you are interviewing for-as much information as possible.
Any terminologies that the company may use.
Sample Questions
Click to read WinRunner or Back to Top
Click to read LoadRunner
Click to read QalityCenter
Click to read Quick_Test_Pro
Click to read SampleQuestions
QTP (Quick Test Professional)
What is an object repository?
What is a virtual object?
What is a checkpoint?
What is object spy?
Why do we need object spy?
What is a smart identification?
What is synchronization?
How many main/major problems are in QTP?>. Synchronization, reorganization and duplication.
What is run time setting?
What think time?
What is modular test?
What is a call to action and copy to action and what is the difference between them?
What is V-user? Same/act like virtual object.
What Optional steps?
Test Director
What is test director?
What do we do with test director?
What are the fields in defect tab?
What is template?
What is a filtering?
What is severity and priority?
How do you generate the report and graphs?
How does test director work?
What is a defect cycle?
Load Runner
What did you do in Load runner?
What are think time and transition time and difference?
Parameterization and why do you do this?
What process and thread?
What multype treat?
What is correlation and how do you do that?
What is scenario?
What is error handling?
What is controller?
Why do you use controller?
How many scenarios in Load Runner?
What call manual and goal oriented scenario?
What is default monitor?
How many components in Load Runner?
S.Q.L (Structured Query Language)
How do you create the table?
How do you update delete and edit?
What is a union?
What is all union?
What is a joint?
How many joints are in joint support?
7. What is view?
No comments:
Post a Comment