BUG BAZZAR

Feb

Posted on 09-02-2011

Filed Under (Questions) by Sathesh on 09-02-2011

1. How Does Run time data (Parameterization) is handled in QTP?

A) 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.

2) What is keyword view and Expert view in QTP?

A) Quick Test’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? Quick Test Professional automatically generates. Any changes made in the Expert View are automatically synchronized with the Keyword View.

3) Explain about the Test Fusion Report of QTP?

A) 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.

4) To which environments does a QTP support?

A) 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.

5) What is QTP?

A) 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…

6) Explain QTP testing process?

A) 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.

6. Analyzing the test results

You examine the test results to pinpoint defects in your application.

7. Reporting defects

As you encounter failures in the application when analyzing test results, you will create defect reports in Defect Reporting Tool.

7) Explain the QTP Tool interface.

A) 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?

A) 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.

9) What are the types of Object Repository’s in QTP?

A) 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.

10) Explain the check points in QTP?

A) . 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

11) In how many ways we can add check points to an application using QTP.

A) 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).

12) How does QTP identifies the object in the application?

A) QTP identifies the object in the application by Logical Name and Class.

For example:

The Edit box is identified by

Logical Name: PSOPTIONS_BSE_TIME20

Class: WebEdit

13) 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?

A) QTP handles those situations using “Regular Expressions”.

14) What is Parameterizing Tests?

A) 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.

15) What is test object model in QTP?

A) 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:

An 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

16) What is Object Spy in QTP?

A) 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.

Supported Check-Points in QTP?

17) What is the Diff between Image check-point and Bit map Check point?

A) 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 is loaded).

Note: The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.

18) How many ways we can parameterize data in QTP?

A) 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.

19. How do u do batch testing in WR & is it possible to do in QTP, if so explain?

Ans: 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.

20. What does it mean when a check point is in red color? what do u do?

Ans : A red color indicates failure. Here we analyze the cause for failure whether it is a Script Issue or Environment Issue or a Application issue.

21. What do you call the window test director – testlab?

Ans : “Execution Grid”. It is place from where we Run all Manual / Automated Scripts

22. How does u create new test sets in TD?

Ans : Login to TD.

Click on “Test Lab” tab.

Select the Desired folder under which we need to Create the Test Set. (Test Sets can be grouped as per module.)

Click on “New Test Set or Ctrl+N” Icon to create a Test Set.

23. How do u do batch testing in WR & is it possible to do in QTP, if so explain?

Ans : You can use Test Batch Runner to run several tests in succession. The results for each test are stored in their default location.

Using Test Batch Runner, you can set up a list of tests and save the list as an .mtb file, so that you can easily run the same batch of tests again, at another time. You can also choose to include or exclude a test in your batch list from running during a batch run.

24. If I give some thousand tests to execute in 2 days what do u do?

Ans : Adhoc testing is done. It covers the least basic functionalities to verify that the system is working fine.

25. How to Import data from a “.xls” file to Data table during Runtime.

Ans : Datatable.Import “…XLS file name…”

DataTable.ImportSheet(FileName, SheetSource, SheetDest)

DataTable.ImportSheet “C:\name.xls” ,1 ,”name”

26. How to export data present in Datatable to an “.xls” file?

Ans : DataTable.Export “….xls file name…”

27. How to get Traceability matrix from TD?

28. How to import a test case present in “.xls” file to TD under a Test set?

29. How to attach a file to TD?

30. What do you to script when objects are removed from application?

31. Syntax for how to call one script from another and Syntax to call one “Action” in another?

Ans: RunAction ActionName, [IterationMode , IterationRange , Parameters]

Here the actions become reusable on making this call to any Action.

IterationRange String Not always required. Indicates the rows for which action iterations will be performed. Valid only when the IterationMode is rngIterations. Enter the row range (i.e. “1-7″), or enter rngAll to run iterations on all rows.

If the action called by the RunAction statement includes an ExitAction statement, the RunAction statement can return the value of the ExitAction’s RetVal argument.

32. How to export QTP results to an “.xls” file?

Ans : (a) By default it creates an “XML” file and displays the results

33. 3 differences between QTP & Winrunner?

Ans :

(a) QTP is object bases Scripting ( VBS) where Winrunner is TSL (C based) Scripting.

(b) QTP supports “.NET” application Automation not available in Winrunner

(d) QTP has “Data Table” to store script values , variables which WR does not have.

(e) Using a “point and click” capability you can easily interface with objects, their definitions and create checkpoints after having recorded a script without having to navigate back to that location in your application like you have to with WinRunner. This greatly speeds up script development.

34. How to create a Runtime property for an object?

35. How to add a runtime parameter to a datasheet?

Ans:

DataTable.LocalSheet

The following example uses the LocalSheet property to return the local sheet of the run-time Data Table in order to add a parameter (column) to it.

MyParam=DataTable.LocalSheet.AddParameter(“Time”, “5:45″)

36. What scripting language is QTP of?

Ans : Vbs

37. Analyzing the Checkpoint results

Standard Checkpoint: By adding standard checkpoints to your tests or components, you can compare the expected values of object properties to the object’s current values during a run session. If the results do not match, the checkpoint fails.

38. Table and DB Checkpoints:

By adding table checkpoints to your tests or components, you can check that a specified value is displayed in a cell in a table on your application. By adding database checkpoints to your tests or components, you can check the contents of databases accessed by your application.

The results displayed for table and database checkpoints are similar. When you run your test or component, QuickTest compares the expected results of the checkpoint to the actual results of the run session. If the results do not match, the checkpoint fails.

You can check that a specified value is displayed in a cell in a table by adding a table checkpoint to your test or component. For ActiveX tables, you can also check the properties of the table object. To add a table checkpoint, you use the Checkpoint Properties dialog box.

Table checkpoints are supported for Web and ActiveX applications, as well as for a variety of external add-in environments.

You can use database checkpoints in your test or component to check databases accessed by your Web site or application and to detect defects. You define a query on your database, and then you create a database checkpoint that checks the results of the query.

Database checkpoints are supported for all environments supported by QuickTest, by default, as well as for a variety of external add-in environments.

There are two ways to define a database query:

(a) Use Microsoft Query. You can install Microsoft Query from the custom installation of Microsoft Office.

(b) Manually define an SQL statement.

The Checkpoint timeout option is available only when creating a table checkpoint. It is not available when creating a database checkpoint

39. Checking Bitmaps:

When you run the test or component, QuickTest compares the object or selected area of the object currently displayed on the Web page or application with the bitmap stored when the test or component was recorded. If there are differences, QuickTest captures a bitmap of the actual object and displays it with the expected bitmap in the details portion of the Test Results window. By comparing the two bitmaps (expected and actual), you can identify the nature of the discrepancy. For more information on test results of a checkpoint, see Viewing Checkpoint Results.

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 is loaded).

Note: The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.

40. Text/Text Area Checkpoint:

In the Text/Text Area Checkpoint Properties dialog box, you can specify the text to be checked as well as which text is displayed before and after the checked text. These configuration options are particularly helpful when the text string you want to check appears several times or when it could change in a predictable way during run sessions.

Note: In Windows-based environments, if there is more than one line of text selected, the Checkpoint Summary pane displays [complex value] instead of the selected text string. You can then click Configure to view and manipulate the actual selected text for the checkpoint.

QuickTest automatically displays the Checked Text in red and the text before and after the Checked Text in blue. For text area checkpoints, only the text string captured from the defined area is displayed (Text Before and Text After are not displayed).

To designate parts of the captured string as Checked Text and other parts as Text Before and Text After, click the Configure button. The Configure Text Selection dialog box opens

Checking XML:

XML (Extensible Markup Language) is a meta-markup language for text documents that is endorsed as a standard by the W3C. XML makes the complex data structures portable between different computer environments/operating systems and programming languages, facilitating the sharing of data.

XML files contain text with simple tags that describe the data within an XML document. These tags describe the data content, but not the presentation of the data. Applications that display an XML document or file use either Cascading Style Sheets (CSS) or XSL Formatting Objects (XSL-FO) to present the data.

You can verify the data content of XML files by inserting XML checkpoints. A few common uses of XML checkpoints are described below:

An XML file can be a static data file that is accessed in order to retrieve commonly used data for which a quick response time is neededâ€”for example, country names, zip codes, or area codes. Although this data can change over time, it is normally quite static. You can use an XML file checkpoint to validate that the data has not changed from one application release to another.

An XML file can consist of elements with attributes and values (character data). There is a parent and child relationship between the elements, and elements can have attributes associated with them. If any part of this structure (including data) changes, your application’s ability to process the XML file may be affected. Using an XML checkpoint, you can check the content of an element to make sure that its tags, attributes, and values have not changed.

XML files are often an intermediary that retrieves dynamically changing data from one system. The data is then accessed by another system using Document Type Definitions (DTD), enabling the accessing system to read and display the information in the file. You can use an XML checkpoint and parameterize the captured data values in order to check an XML document or file whose data changes in a predictable way.

XML documents and files often need a well-defined structure in order to be portable across platforms and development systems. One way to accomplish this is by developing an XML schema, which describes the structure of the XML elements and data types. You can use schema validation to check that each item of content in an XML file adheres to the schema description of the element in which the content is to be placed.

41. Object Repositories types, which & when to use?

Deciding Which Object Repository Mode to Choose

To choose the default object repository mode and the appropriate object repository mode for each test, you need to understand the differences between the two modes.

In general, the object repository per-action mode is easiest to use when you are creating simple record and run tests, especially under the following conditions:

You have only one, or very few, tests that correspond to a given application, interface, or set of objects.

You do not expect to frequently modify test object properties.

You generally create single-action tests.

Conversely, the shared object repository mode is generally the preferred mode when:

You have several tests that test elements of the same application, interface, or set of objects.

You expect the object properties in your application to change from time to time and/or you regularly need to update or modify test object properties.

You often work with multi-action tests and regularly use the Insert Copy of Action and Insert Call to Action options.

42. Can we Script any test case with out having Object repository? or Using Object Repository is a must?

Ans: No. U can script with out Object repository by knowing the Window Handlers, spying and recognizing the objects logical names and properties available.

43. How to execute a WinRunner Script in QTP?

Ans : (a) TSLTest.RunTest TestPath, TestSet [, Parameters ] –> Used in QTP 6.0 used for backward compatibility

Parameters : The test set within Quality Center, in which test runs are stored. Note that this argument is relevant only when working with a test in a Quality Center project. When the test is not saved in Quality Center, this parameter is ignored.

e.g : TSLTest.RunTest “D:\test1″, “”

(b)

TSLTest.RunTestEx TestPath, RunMinimized, CloseApp [, Parameters ]

TSLTest.RunTestEx “C:\WinRunner\Tests\basic_flight”, TRUE, FALSE, “MyValue”

CloseApp : Indicates whether to close the WinRunner application when the WinRunner test run ends.

Parameters : Up to 15 WinRunner function argument

44. How to handle Run-time errors?

(a) On Error Resume Next : causes execution to continue with the statement immediately following the statement that caused the run-time error, or with the statement immediately following the most recent call out of the procedure containing the On Error Resume Next statement. This allows execution to continue despite a run-time error. You can then build the error-handling routine inline within the procedure.

Using “Err” object msgbox “Error no: ” & “ ” & Err.Number & “ ” & Err.description & “ ” & Err.Source & Err.HelpContext

45. How to change the run-time value of a property for an object?

Ans : SetTOProperty changes the property values used to identify an object during the test run.

Only properties that are included in the test object description can be set

46. How to retrieve the property of an object?

Ans : using “GetRoProperty”.

47. How to open any application during Scripting?

Ans : SystemUtil , object used to open and close applications and processes during a run session.

(a) A SystemUtil.Run statement is automatically added to your test when you run an application from the Start menu or the Run dialog box while recording a test

E.g : SystemUtil.Run “Notepad.exe”

SystemUtil.CloseDescendentProcesses (Closes all the processes opened by QTP)

48. Types of properties that Quick Test learns while recording?

Ans : (a) Mandatory (b) Assistive .

In addition to recording the mandatory and assistive properties specified in the Object Identification dialog box, QuickTest can also record a backup ordinal identifier for each test object. The ordinal identifier assigns the object a numerical value that indicates its order relative to other objects with an otherwise identical description (objects that have the same values for all properties specified in the mandatory and assistive property lists). This ordered value enables QuickTest to create a unique description when the mandatory and assistive properties are not sufficient to do so.

49. What is the extension of script and object repository files?

Ans : Object Repository : .tsr , Script : .mts, Excel : Default.xls

50. How to supress warnings from the “Test results page”?

Ans : From the Test results Viewer “Tools > Filters > Warnings”…must be “Unchecked”.

51. When we try to use test run option “Run from Step”, the browser is not launching automatically why?

Ans : This is default behaviour.

52. Does QTP is “Unicode” compatible?

Ans : QTP 6.5 is not but QTP 8.0 is expected to be Unicode compatabile by end of December 2004.

53. How to “Turn Off” QTP results after running a Script?

Ans : Goto “Tools > Options > Run Tab” and Deselect “View results when run session ends”. But this supresses only the result window, but a og will be created and can viewed manulaly which cannot be restricted from getting created.

54. How to get “FontSize” of a “WebEdit”?

55. Is there anyway to automatically update the Datasource name in Database Checkpoints object when we migrate tests to a new release?

56. How to verify the Cursor focus of a certain field?

Ans : Use “focus” property of “GetRoProperty” method”

57. Any limitation to XML Checkpoints?

Ans : Mercury has determined that 1.4MB is the maximum size of a XML file that QTP 6.5 can handle

58. How to make arguments optional in a function?

Ans : this is not possible as default VBS doesn’t support this. Instead you can pass a blank scring and have a default value if arguments r not required.

59. How to covert a String to an integer?

Ans : CInt()—> a conversion function available.

60. Inserting a Call to Action is not importing all columns in Datatable of globalsheet. Why?

Ans : Inserting a call to action will only Import the columns of the Action called

(0) Comments Read More

Nov

Posted on 27-11-2010

Types of Software Testing- Whitebox Testing

Filed Under (Software Testing) by Sathesh on 27-11-2010

UNIT TESTING

The developer carries out unit testing in order to check if the particular module or unit of code is working fine. The Unit Testing comes at the very basic level as it is carried out as and when the unit of the code is developed or a particular functionality is built. Unit testing deals with testing a unit as a whole. This would test the interaction of many functions but confine the test within one unit. The exact scope of a unit is left to interpretation. Supporting test code, sometimes called scaffolding, may be necessary to support an individual test. This type of testing is driven by the architecture and implementation teams. This focus is also called black-box testing because only the details of the interface are visible to the test. Limits that are global to a unit are tested here. In the construction industry, scaffolding is a temporary, easy to assemble and disassemble, frame placed around a building to facilitate the construction of the building. The construction workers first build the scaffolding and then the building. Later the scaffolding is removed, exposing the completed building. Similarly, in software testing, one particular test may need some supporting software. This software establishes an environment around the test. Only when this environment is established can a correct evaluation of the test take place. The scaffolding software may establish state and values for data structures as well as providing dummy external functions for the test. Different scaffolding software may be needed from one test to another test. Scaffolding software rarely is considered part of the system. Sometimes the scaffolding software becomes larger than the system software being tested. Usually the scaffolding software is not of the same quality as the system software and frequently is quite fragile. A small change in the test may lead to much larger changes in the scaffolding. Internal and unit testing can be automated with the help of coverage tools. A coverage tool analyzes the source code and generates a test that will execute every alternative thread of execution. It is still up to the programmer to combine this test into meaningful cases to validate the result of each thread of execution. Typically, the coverage tool is used in a slightly different way. First the coverage tool is used to augment the source by placing informational prints after each line of code. Then the testing suite is executed generating an audit trail
. This audit trail is analyzed and reports the percent of the total system code executed during the test suite. If the coverage is high and the untested source lines are of low impact to the system’s overall quality, then no more additional tests are required.

STATIC & DYNAMIC ANALYSIS

Static analysis involves going through the code in order to find out any possible defect in the code. Dynamic analysis involves executing the code and analyzing the output.

STATEMENT COVERAGE

In this type of testing the code is executed in such a manner that every statement of the application is executed at least once. It helps in assuring that all the statements execute without any side effect.

BRANCH COVERAGE

No software application can be written in a continuous mode of coding, at some point we need to branch out the code in order to perform a particular functionality. Branch coverage testing helps in validating of all the branches in the code and making sure that no branching leads to abnormal behaviour of the application.

SECURITY TESTING

Security Testing is carried out in order to find out how well the system can protect itself from unauthorized access, hacking – cracking, any code damage etc. which deals with the code of application. This type of testing needs sophisticated testing techniques.

MUTATION TESTING

A kind of testing in which, the application is tested for the code that was modified after fixing a particular bug/defect. It also helps in finding out which code and which strategy of coding can help in developing the functionality effectively.

(0) Comments Read More

Nov

Posted on 27-11-2010

Types of Software Testing- Blackbox Testing

Filed Under (Software Testing) by Sathesh on 27-11-2010

FUNCTIONAL TESTING

In this type of testing, the software is tested for the functional requirements. The tests are written in order to check if the application behaves as expected. Although functional testing is often done toward the end of the development cycle, it can—and should, —be started much earlier. Individual components and processes can be tested early on, even before it’s possible to do functional testing on the entire system. Functional testing covers how well the system executes the functions it is supposed to execute—including user commands, data manipulation, searches and business processes, user screens, and integrations. Functional testing covers the obvious surface type of functions, as well as the back-end operations (such as security and how upgrades affect the system).

STRESS TESTING

The application is tested against heavy load such as complex numerical values, large number of inputs, large number of queries etc. which checks for the stress/load the applications can withstand. Stress testing deals with the quality of the application in the environment. The idea is to create an environment more demanding of the application than the application would experience under normal workloads. This is the hardest and most complex category of testing to accomplish and it requires a joint effort from all teams. A test environment is established with many testing stations. At each station, a script is exercising the system. These scripts are usually based on the regression suite. More and more stations are added, all simultaneous hammering on the system, until the system breaks. The system is repaired and the stress test is repeated until a level of stress is reached that is higher than expected to be present at a customer site. Race conditions and memory leaks are often found under stress testing. A race condition is a conflict between at least two tests. Each test works correctly when done in isolation. When the two tests are run in parallel, one or both of the tests fail. This is usually due to an incorrectly managed lock. A memory leak happens when a test leaves allocated memory behind and does not correctly return the memory to the memory allocation scheme. The test seems to run correctly, but after being exercised several times, available memory is reduced until the system fails.

LOAD TESTING

The application is tested against heavy loads or inputs such as testing of web sites in order to find out at what point the web-site/application fails or at what point its performance degrades. Load testing operates at a predefined load level, usually the highest load that the system can accept while still functioning properly. Note that load testing does not aim to break the system by overwhelming it, but instead tries to keep the system constantly humming like a well-oiled machine. In the context of load testing, extreme importance should be given of having large datasets available for testing. Bugs simply do not surface unless you deal with very large entities such thousands of users in repositories such as LDAP/NIS/Active Directory; thousands of mail server mailboxes, multi-gigabyte tables in databases, deep file/directory hierarchies on file systems, etc. Testers obviously need automated tools to generate these large data sets, but fortunately any good scripting language worth its salt will do the job.

AD-HOC TESTING

This type of testing is done without any formal Test Plan or Test Case creation. Ad-hoc testing helps in deciding the scope and duration of the various other testing and it also helps testers in learning the application prior starting with any other testing. It is the least formal method of testing. One of the best uses of ad hoc testing is for discovery. Reading the requirements or specifications (if they exist) rarely gives you a good sense of how a program actually behaves. Even the user documentation may not capture the “look and feel” of a program. Ad hoc testing can find holes in your test strategy, and can expose relationships between subsystems that would otherwise not be apparent. In this way, it serves as a tool for checking the completeness of your testing. Missing cases can be found and added to your testing arsenal. Finding new tests in this way can also be a sign that you should perform root cause analysis. Ask yourself or your test team, “What other tests of this class should we be running?” Defects found while doing ad hoc testing are often examples of entire classes of forgotten test cases. Another use for ad hoc testing is to determine the priorities for your other testing activities. In our example program, Panorama may allow the user to sort photographs that are being displayed. If ad hoc testing shows this to work well, the formal testing of this feature might be deferred until the problematic areas are completed. On the other hand, if ad hoc testing of this sorting photograph feature uncovers problems, then the formal testing might receive a higher priority.

EXPLORATORY TESTING

This testing is similar to the ad-hoc testing and is done in order to learn/explore the application. Exploratory software testing is a powerful and fun approach to testing. In some situations, it can be orders of magnitude more productive than scripted testing. At least unconsciously, testers perform exploratory testing at one time or another. Yet it doesn’t get much respect in our field. It can be considered as “Scientific Thinking” at real time

USABILITY TESTING

This testing is also called as ‘Testing for User-Friendliness’. This testing is done if User Interface of the application stands an important consideration and needs to be specific for the specific type of user. Usability testing is the process of working with end-users directly and indirectly to assess how the user perceives a software package and how they interact with it. This process will uncover areas of difficulty for users as well as areas of strength. The goal of usability testing should be to limit and remove difficulties for users and to leverage areas of strength for maximum usability. This testing should ideally involve direct user feedback, indirect feedback (observed behaviour), and when possible computer supported feedback. Computer supported feedback is often (if not always) left out of this process. Computer supported feedback can be as simple as a timer on a dialog to monitor how long it takes users to use the dialog and counters to determine how often certain conditions occur (i.e. error messages, help messages, etc). Often, this involves trivial modifications to existing software, but can result in tremendous return on investment. Ultimately, usability testing should result in changes to the delivered product in line with the discoveries made regarding usability. These changes should be directly related to real-world usability by average users. As much as possible, documentation should be written supporting changes so that in the future, similar situations can be handled with ease.

SANITY TESTING

Sanity testing checks for the behaviour of the system. This type of software testing is also called as Narrow Regression Testing.

PARALLEL TESTING

Parallel testing is done by comparing results from two different systems like old vs new or manual vs automated.
Installation Testing: This type of software testing identifies the ways in which installation procedure leads to incorrect results.

COMPATIBILITY TESTING

Compatibility Testing determines if an application under supported configurations perform as expected, with various combinations of hardware and software packages. Read more on compatibility testing.
CONFIGURATION TESTING

This testing is done to test for compatibility issues. It determines minimal and optimal configuration of hardware and software, and determines the effect of adding or modifying resources such as memory, disk drives, and CPU.

COMPLIANCE TESTING

This type of testing checks whether the system was developed in accordance with standards, procedures, and guidelines.

ERROR HANDLING TESTING

This software testing type determines the ability of the system to properly process erroneous transactions.

MANUAL SUPPORT TESTING

This type of software testing is an interface between people and application system.

INTER SYSTEM TESTING

This type of software testing method is an interface between two or more application systems.

EXPLORATORY TESTIG

Exploratory Testing is a type of software testing, which is similar to ad-hoc testing, and is performed to explore the software features. Read more on exploratory testing.

SMOKE TESTING

This type of testing is also called sanity testing and is done in order to check if the application is ready for further major testing and is working properly without failing up to least expected level. A test of new or repaired equipment by turning it on. If it smokes… guess what… it doesn’t work! The term also refers to testing the basic functions of software. The term was originally coined in the manufacture of containers and pipes, where smoke was introduced to determine if there were any leaks. A common practice at Microsoft and some other shrink-wrap software companies is the “daily build and smoke test” process. Every file is compiled, linked, and combined into an executable program every day, and the program is then put through a “smoke test”, a relatively simple check to see whether the product “smokes” when it runs.

RECOVERY TESTING

Recovery testing is basically done in order to check how fast and better the application can recover against any type of crash or hardware failure etc. Type or extent of recovery is specified in the requirement specifications. It is basically testing how well a system recovers from crashes, hardware failures, or other catastrophic problems

VOLUME TESTING

Volume testing is done against the efficiency of the application. Huge amount of data is processed through the application (which is being tested) in order to check the extreme limitations of the system
Volume Testing, as its name implies, is testing that purposely subjects a system (both hardware and software) to a series of tests where the volume of data being processed is the subject of the test. Such systems can be transactions processing systems capturing real time sales or could be database updates and or data retrieval.
Volume testing will seek to verify the physical and logical limits to a system’s capacity and ascertain whether such limits are acceptable to meet the projected capacity of the organization’s business processing.

DOMAIN TESTING

Domain testing is the most frequently described test technique. Some authors write only about domain testing when they write about test design. The basic notion is that you take the huge space of possible tests of an individual variable and subdivide it into subsets that are (in some way) equivalent. Then you test a representative from each subset.

SCENARIO TESTING
Scenario tests are realistic, credible, and motivating to stakeholders, challenging for the program and easy to evaluate for the tester. They provide meaningful combinations of functions and variables rather than the more artificial combinations you get with domain testing or combinatorial test design.

REGRESSION TESTING

Regression testing is a style of testing that focuses on retesting after changes are made. In traditional regression testing, we reuse the same tests (the regression tests). In risk-oriented regression testing, we test the same areas as before, but we use different (increasingly complex) tests. Traditional regression tests are often partially automated. These note focus on traditional regression.
Regression testing attempts to mitigate two risks:
o A change that was intended to fix a bug failed.
o Some change had a side effect, unfixing an old bug or introducing a new bug

Regression testing approaches differ in their focus. Common examples include:
Bug regression: We retest a specific bug that has been allegedly fixed.
Old fix regression testing: We retest several old bugs that were fixed, to see if they are back. (This is the classical notion of regression: the program has regressed to a bad state.)
General functional regression: We retest the product broadly, including areas that worked before, to see whether more recent changes have destabilized working code. (This is the typical scope of automated regression testing.)
Conversion or port testing: The program is ported to a new platform and a subset of the regression test suite is run to determine whether the port was successful. (Here, the main changes of interest might be in the new platform, rather than the modified old code.)
Configuration testing: The program is run with a new device or on a new version of the operating system or in conjunction with a new application. This is like port testing except that the underlying code hasn’t been changed–only the external components that the software under test must interact with.
Localization testing: The program is modified to present its user interface in a different language and/or following a different set of cultural rules. Localization testing may involve several old tests (some of which have been modified to take into account the new language) along with several new (non-regression) tests.
Smokes testing also known as build verification testing: A relatively small suite of tests is used to qualify a new build. Normally, the tester is asking whether any components are so obviously or badly broken that the build is not worth testing or some components are broken in obvious ways that suggest a corrupt build or some critical fixes that are the primary intent of the new build didn’t work. The typical result of a failed smoke test is rejection of the build (testing of the build stops) not just a new set of bug reports.

USER ACCEPTANCE TESTING

In this type of testing, the software is handed over to the user in order to find out if the software meets the user expectations and works as it is expected to. In software development, user acceptance testing (UAT) – also called beta testing, application testing, and end user testing – is a phase of software development in which the software is tested in the “real world” by the intended audience. UAT can be done by in-house testing in which volunteers or paid test subjects use the software or, more typically for widely-distributed software, by making the test version available for downloading and free trial over the Web. The experiences of the early users are forwarded back to the developers who make final changes before releasing the software commercially.

ALPHA TESTING

In this type of testing, the users are invited at the development centre where they use the application and the developers note every particular input or action carried out by the user. Any type of abnormal behaviour of the system is noted and rectified by the developers.

BETA TESTING

In this type of testing, the software is distributed as a beta version to the users and users test the application at their sites. As the users explore the software, in case if any exception/defect occurs that is reported to the developers. Beta testing comes after alpha testing. Versions of the software, known as beta versions, are released to a limited audience outside of the company. The software is released to groups of people so that further testing can ensure the product has few faults or bugs. Sometimes, beta versions are made available to the open public to increase the feedback field to a maximal number of future users.

(0) Comments Read More

Nov

Posted on 20-11-2010

Software Testing Principles

Filed Under (Software Testing) by Sathesh on 20-11-2010

Principle #1: Complete testing is impossible.

Principle #2: Software testing is not simple.
Reasons:
Quality testing requires testers to understand a system/product completely
Quality testing needs adequate test set, and efficient testing methods
A very tight schedule and lack of test tools.

Principle #3: Testing is risk-based.

Principle #4: Testing must be planned.

Principle #5: Testing requires independence.

Principle #6: Quality software testing depends on:
Good understanding of software products and related domain application
Cost-effective testing methodology, coverage, test methods, and tools.
Good engineers with creativity, and solid software testing experience

QTP Question 04: How Does Run time data (Parameterization) is handled in QTP?

You can then enter test data into the Data Table, an integratedspreadsheet with the full functionality of Excel, to manipulate datasets and create multiple test iterations, without programming, toexpand test case coverage. Data can be typed in or imported fromdatabases, spreadsheets, or text files.

QTP Question 05: What is keyword view and Expert view in QTP?

QuickTest’s Keyword Driven approach, test automation expertshave full access to the underlying test and object properties, via anintegrated scripting and debugging environment that is round-tripsynchronized with the Keyword View.Advanced testers can view and edit their tests in the Expert View,which reveals the underlying industry-standard VBScript thatQuickTest Professional automatically generates. Any changesmade in the Expert View are automatically synchronized with theKeyword View.

QTP Question 06: Explain about the Test Fusion Report of QTP?

Once a tester has run a test, a TestFusion report displays allaspects of the test run: a high-level results overview, an expandableTree View of the test specifying exactly where application failuresoccurred, the test data used, application screen shots for every stepthat highlight any discrepancies, and detailed explanations of eachcheckpoint pass and failure. By combining TestFusion reports withQuickTest Professional, you can share reports across an entire QAand development team.

QTP Question 07: 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.

QTP Question 08: What is QTP or Quick Test Pro?

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.

QTP Question 09: Explain the QTP Tool interface?

QTP Tool interface 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

QTP Question 10: 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.

QTP Question 11: What are the types of Object Repositorys 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.

QTP Question 12: Explain the check points 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.

v A page checkpoint checks the characteristics of a Application

v A text checkpoint checks that a text string is displayed in the appropriate place on a Application.

v An object checkpoint (Standard) checks the values of an object on a Application.

v An image checkpoint checks the values of an image on a Application.

v A table checkpoint checks information within a table on a Application

v An Accessibility checkpoint checks the web page for Section 508 compliance.

v An XML checkpoint checks the contents of individual XML data files or XML documents that are part of your Web application.

v A database checkpoint checks the contents of databases accessed by your web site

QTP Question 13: In how many ways we can add check points 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).

QTP Question 14: How does QTP identifies the object in the application?

QTP identifies the object in the application by LogicalName and Class.
For example:
The Edit box is identified by

v Logical Name : PSOPTIONS_BSE_TIME20

v Class: WebEdit

QTP Question 15: If an application name is changes frequently i.e while recording it has name, in this case how does QTP handles?

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 are the Features & Benefits of Quick Test Pro (QTP 8.0)? – Operates stand-alone, or integrated into Mercury Business Process Testing and Mercury Quality Center. Introduces next-generation zero-configuration Keyword Driven testing technology in Quick Test Professional 8.0 allowing for fast test creation, easier maintenance, and more powerful data-driving capability. Identifies objects with Unique Smart Object Recognition, even if they change from build to build, enabling reliable unattended script execution. Collapses test documentation and test creation to a single step with Auto-documentation technology. Enables thorough validation of applications through a full complement of checkpoints.
How to handle the exceptions using recovery scenario manager in QTP? – There are 4 trigger events during which a recovery scenario should be activated. A pop up window appears in an opened application during the test run: A property of an object changes its state or value, A step in the test does not run successfully, An open application fails during the test run, These triggers are considered as exceptions. You can instruct QTP to recover unexpected events or errors that occurred in your testing environment during test run. Recovery scenario manager provides a wizard that guides you through the defining recovery scenario. Recovery scenario has three steps: 1. Triggered Events 2. Recovery steps 3. Post Recovery Test-Run
What is the use of Text output value in QTP? – Output values enable to view the values that the application talks during run time. When parameterized, the values change for each iteration. Thus by creating output values, we can capture the values that the application takes for each run and output them to the data table.
How to use the Object spy in QTP 8.0 version? – There are two ways to Spy the objects in QTP: 1) thru file toolbar, In the File Toolbar click on the last toolbar button (an icon showing a person with hat). 2) True Object repository Dialog, In Object repository dialog click on the button object spy. In the Object spy Dialog click on the button showing hand symbol. The pointer now changes in to a hand symbol and we have to point out the object to spy the state of the object if at all the object is not visible. or window is minimized then, hold the Ctrl button and activate the required window to and release the Ctrl button.
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? – Quick Test’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 Quick Test 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 Test Fusion 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 Test Fusion reports with Quick Test Professional, you can share reports across an entire QA and development team.
Which environments does QTP support? – Quick Test 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? – Quick Test 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, Quick Test 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

10. Explain QTP Testing process? – Quick Test testing process consists of 6 main phases:

11. 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.

12. Recording a session on your application – As you navigate through your application, Quick Test 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.

13. 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.

14. Debugging your test – If changes were made to the script, you need to debug it to check that it operates smoothly and without interruption.

15. Running your test on a new version of your application – You run a test to check the behavior of your application. While running, Quick Test connects to your application and performs each step in your test.

16. Analyzing the test results – You examine the test results to pinpoint defects in your application.

17. Reporting defects – As you encounter failures in the application when analyzing test results, you will create defect reports in Defect Reporting Tool.

18. 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 Quick Test 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 Quick Test for the first time. You can display the Debug toolbar by choosing View — Toolbars — Debug. 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 Quick Test 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. 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

19. How does QTP recognize Objects in AUT? – Quick Test stores the definitions for application objects in a file called the Object Repository. As you record your test, Quick Test will add an entry for each item you interact with. Each Object Repository entry will be identified by a logical name (determined automatically by Quick Test), and will contain a set of properties (type, name, etc) that uniquely identify each object. Each line in the Quick Test 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.

20. What are the types of Object Repositories in QTP? – Quick Test 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, Quick Test 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.

21. Explain the check points in QTP? – A checkpoint verifies that expected information is displayed in an 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 an Application. A text checkpoint checks that a text string is displayed in the appropriate place on an Application. An object checkpoint (Standard) checks the values of an object on an Application. An image checkpoint checks the values of an image on an Application. A table checkpoint checks information within a table on a Application. An Accessibilityy 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

22. In how many ways we can add check points 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).

23. How does QTP identify objects in the application? – QTP identifies the object in the application by Logical Name and Class.

24. What is Parameterizing 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.

25. What is test object model in QTP? – The test object model is a large set of object types or classes that Quick Test 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 Quick Test can record for it. A test object is an object that Quick Test creates in the test or component to represent the actual object in your application. Quick Test stores information about the object that will help it identify and check the object during the run session.

26. 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.

27. What is the Diff between Image check-point and Bit map Check point? – 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. Quick Test 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.

28. 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, Quick Test 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 Quick Test 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 Quick Test generate a random number and insert it in a number of tickets edit field.

29. How do u 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 Test set from the Execution Grid. The same is possible with QTP also. If our test cases are automated then by selecting Run Test set 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.

30. If I give some thousand tests to execute in 2 days what do u do? – Adhoc testing is done. It Covers the least basic functionalities to verify that the system is working fine.

31. What does it mean when a check point is in red color? what do u do? – A red color indicates failure. Here we analyze the cause for failure whether it is a Script Issue or Environment Issue or a Application issue.

32. 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.

33. What is the file extension of the code file & object repository file in QTP? – Code file extension is.vbs and object repository is.tsr

34. 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. Quicktest 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.

35. What are the properties you would use for identifying a browser & page when using descriptive programming? – Name would be another property apart from title that we can use.

36. Give me an example where you have used a COM interface in your QTP project? – com interface 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 will be one among those interfaces. 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).

37. Explain in brief about the QTP Automation Object Model. – Essentially all configuration and run functionality provided via the Quick Test interface is in some way represented in the Quick Test automation object model via objects, methods, and properties. Although a one-on-one comparison cannot always be made, most dialog boxes in Quick Test 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 Quick Test automation object model, along with standard programming elements such as loops and conditional statements to design your program.

(0) Comments Read More

Oct

Posted on 01-10-2010

QTP Questions

Filed Under (Questions) by Sathesh on 01-10-2010

1) ‘Browser navigation timeout’ is in which tab of Test Settings (File->Settings) window.

A) Properties
B) Resources
C) Web
D) Web Settings

2) How many tabs are there in Test Settings (File->Settings) window

A) 7
B) 6
C) 5
D) 8

3) Identify the tabs in the Test Settings (File->Settings) window

A) Properties, Run, Resources, Parameters, Environment, Web, Recovery
B) Properties, Run, Resources, Parameters, Environment, Web Settings,Recovery
C) Properties, Run Options, Resources, Parameters, Environment, Web, Recovery
D) Properties, Run, Resources, Input Parameters, Environment, Web, Recovery

4) ‘Generate Script’ is in which tab of Test Settings (File->Settings) window

A) Properties
B) Web
C) Resources
D) Recovery

5) The following are the four main columns in the Keyword view

A) Item, Operation, Value, Comments
B) Item, Operation, Value, Documentation
C) Item, Operation, Property, Documentation
D) Number, Operation, Value, Documentation

6) For each object and method in an Expert View statement, a corresponding row exists in the Keyword View.

A) True
B) False
C) There is a problem with the statement.
D) None of above

7) You can work on one or several function libraries at the same time.

A) True
B) False

You can insert additional steps on the test objects captured in the Active screen after the recording session.

A) True
B) False

9) The Active Screen enables you to parameterize object values and insert checkpoints

A) True
B) False

10) A QTP user can increase or decrease the active screen information saved with the test.

A) True
B) False

11) The Information pane provides a list of…………. in the test:

A) Semantic errors
B) Syntax errors
C) Common errors
D) Logic errors

12) When we switch from Expert view to the Keyword view, QTP automatically checks for syntax errors in the test and shows them in the information pane.

A) True
B) False

13) If the information pane is not open, QTP automatically opens it in case a syntax error is detected.

A) True
B) False

14) ………………… provides a list of the resources that are specified in your test but cannot be found.

A) Missing pane
B) Missing Resources pane
C) Resources pane
D) Missing Items pane

15) Whenever you open a test or a function library, QTP automatically checks for the availiblity of specified resources.

A) True
B) False

16) The Data Table does not assists you in parameterizing your test.

A) True
B) False

17) Tabs in the Debug Viewer pane are:

A) Watch, Variables, Debug
B) Watch, Data, Command
C) Watch, Variables, Command
D) View, Variables, Command

18) …………… tab enables you to view the current value of any variable or VBScript expression.

A) Watch
B) VIew
C) Locate
D) Current

19) The …. tab displays the current value of all variables that have been recognized up to the last step performed in the run session.

A) View
B)Variables
C) Locate
D) Current

20) The ………tab enables you to run a line of script to set or modify the current value of a variable or VBScript object in your test or function library.

A) View
B) Variables
C) Command
D) Current

21) Panes in QTP can have one of the following states—docked or floating.

A) True
B) False

22) Which of the following statement is True:

A) QuickTest enables you to open and work on one test at a time
B) QuickTest enables you to open and work on two tests at a time
C) QuickTest enables you to open and work on predefined number of tests at a time
D) QuickTest enables you to open and work on nine test at a time

23) Which of the following statement is True:

A) You can open and work on two function libraries simultaneously
B) You can open and work on multiple function libraries simultaneously
C) You can open and work on nine function libraries simultaneously
D) You can open and work on one function library at a time

24) You can open any function library, regardless of whether it is associated with the currently open test.

A) True
B) False

25) You can work with multiple documents (test, component, or application area, function libraries) using the…… dialog box

A) Panes
B) Display
C) Show
D) Windows

26) QuickTest has ….. built-in toolbars.

A) 5
B) 6
C) 7
D) 8

27) The ……… toolbar contains buttons for recording and running your test.

A) Standard
B) Tools
C) Automation
D) Edit

28) Shortcut Key for opening a new Function Library is:

A) Shift+Alt+N
B) Ctrl+Alt+N
C) Shift+N
D) CRTL+N

29) Shortcut Key for Closing all open Function Libraries in one go.

A) Ctrl+Alt+C
B) Shift+A+C
B)Shift+N
D) None of these

30) shortcut Key for Commenting out the current row, or selected rows

A) Shift+M
B) Ctrl+C
C) Ctrl+M
D) Shift+C

31) You can manage the test actions and the test or function library steps using the … menu commands

A) File
B) Edit
C) Automation
D) Tools

32) To expand all the steps in the keyword view which option you would use from the View menu.

A) Expand
B) Expand All
C) Expand Items
D) Expand Rows

33) What is the shortcut key to open a Step Generator.

A) F2
B) F5
C) F6
D) F7

34) Function Definition Generator in found in which menu option.

A) File
B) Tools
C) Insert
D) View

35) The shortcut keys for Record, Stop and Run respectively are

A) F3, F4, F5
B) F4, F3, F5
C) F4, F5, F3
D) F3, F5, F4

36) What is the shortcut key for opening an Object Repository.

A) Alt+R
B) Shift+R
C) Ctrl+R
D) Shift+O+R

37) Shortcut key to Insert/Remove a breakpoint is

A) F9
B) F8
C) Ctrl+b
D) Shift+b

38) ………runs only the current line of the script. If the current line calls a method, the method is displayed in the view but is not performed.

A) Step Over
B) Step Out
C) Step Into
D) Step Till

39) ………runs only the current line of the script. When the current line calls a method, the method is performed in its entirety, but is not displayed in the view.

A) Step Over
B) Step Out
C) Step Into
D) Step Till

40) What is the shortcut key to Clear all Breakpoints

A) Ctrl+Shift+F9
B) Shift+Ctrl+F9
C) Alt+Shift+F9
D) Alt+Ctrl+F9

41) Object Spy can be found in ……..menu.

A) Tool
B) Tools
C) Task
D) Tasks

42) ………… displays the open documents side-by-side.

A) Tile Vertically
B) Tile Horizontally
C) Cascade
D) Tile Cascade

43) For opening the QuickTest Professional Help we can use…….

A) F3
B) F5
C) F1
D) F2

44) If QTP cannot find any object that matches the description, or if it finds more than one object that matches, QuickTest may use the…………mechanism to identify the object.

A) Ordinal Identifier
B) Index Identifier
C) Smart Identification
D) Assistive Identification

45) You can configure the …….., ………… and …………
properties that QuickTest uses to record descriptions of the objects in your application

A) mandatory, assistive, and ordinal identifier
B) mandatory, required, and ordinal identifier
C) smart, assistive, and ordinal identifier
D) Index, assistive, and ordinal identifier

46) The ………. property set for each test object is created and maintained by QuickTest.

A) Run-Time Object
B) Test Object
C) Smart Identification Object
D) Assistive Object

47)You can access and perform ……… methods using the Object property.

A) Run-Time Object
B) Test Object
C) Smart Identification Object
D) Assistive Object

48) You can view or modify the test object property values that are stored with your test in the ………

A) Information Pane
B) Data Table
C) Information Pane & Data Table Both
D) Object Properties & Object Repository dialog box.

49) You can retrieve or modify property values of the test object during the run session by adding ……….statements in the Keyword View or Expert View.

A) GetROProperty & SetROProperty
B) GetTOProperty & SetTOProperty
C) GetTOProperty & SetROProperty
D) GetROProperty & SetTOProperty

50) If the available test object methods or properties for an object do not provide the functionality you need, you can access …………..of any run-time object using the Object property.

A) The internal methods and properties
B) The mandatory methods and properties
C) The selective methods and properties
D) The assistive methods and properties

51) Using the Object Spy, you can view

A) the run-time or test object properties and methods of any object in an open application.
B) the run-time or test object properties of any object in an open application.
C) the test object properties and methods of any object in an open application.
D) the run-time object properties and methods of any object in an open application.

52) There are ………object type filters in Object spy dialog box.

A) Two
B)Three
C) Four
D) Five

53) In the Object Spy window, in the Properties Tab

A) Copying of Properties and its values is possible with CTRL+C
B) Copying of Properties and its values is possible by right clicking on it and choosing copy.
C) Copying of Properties and its values is possible with both A) and B) methods
D) Copying of Properties and its values is possible is not possible

54) In the Object Spy window, in the methods Tab

A) Copying of Methods is possible with CTRL+C
B) Copying of Methods is possible by right clicking on it and choosing copy.
C) Copying of Methods is possible with both A) and B) methods
D) Copying of Methods is possible is not possible

55) Object Spy dialog box

A) Can be resized
B) Cannot be resized

56) ………….. are the highest level of the test hierarchy in the
Keyword view.

A) Tests
B) Steps
C) Call to Actions
D) Actions

57) You can copy and paste or drag and drop actions to move them to a different location within a test

A) True
B) False

58) You can print the contents of the Keyword View to your Windows default printer (and even preview the contents prior to printing).

A) True
B) False

59) In the Keyword View, you can also view properties for items such as checkpoints.

A) True
B) False

60) In the step Browser > Page > Edit > Set “Sachin”, identify container object(s)

A) Browser
B) Edit
C) Page
D) Both Browser & Page

61) You can use the Keyword View to add a step ……….in your test.

A) at the end
B) below the currently selected step
C) at the beginning
D) at anypoint

62) The Documentation cell is ………….

A) Read-only
B) Write-only
C) Read and Write
D) Read, write & execute

63) An Item column can be any of the following:

A) A test object
B) A statement like Dim
C) A step generated by step generator
D) All of above

64) The Operation cell in the keyword view specifies the operation to be performed on the item listed in the ……….. column.

A) Operation
B) Documentation
C) Item
D) Value

65) Even if the Item column in the Keyword View is displayed to the right of the Operation column, you must still first select an item to view the list of available operations in the Operation column.

A) True
B) False

66) The Value cell in the keyword view can contain…….. value

A) Constant
B) Parameter
C) Both A) & B)
D) None of these

67)The …………… enables you to encode your passwords and place secure values into the Data Table.

A) Password Encoder
B) Password Decoder
C) Password Encode
D) Password Decode

68) You can also encrypt strings in Data Table cells using the ……… option in the Data Table menu.

A) Decrypt
B) Encrypt
C) Encrypt Code
D) Decrypt Code

69) In addition to adding standard statement steps to your test using the Keyword View, you can also insert

A) Checkpoint step
B) Output value step
C) Comment step
D) All of above

70) The correct syntax of the conditiona statement starting with Do is…..

A) Do…While
B) Do…Until
C) Do…Next
D) Both A) and B)

71) QuickTest processes a comments when it runs a test.

A) True
B) False

72) Press ….. to add a new step below the currently selected step.

A) F8
B) Shift + A
C) F0
D) Shift + A + Q

73) While working with the Keyword View, you can …… steps to move them to a different location in a test or in an action

A) Copy and Paste
B) Cut and Paste
C) Drag and drop
D) Both A) and C)

74) You can specify the order in which the columns are displayed in the Keyword view.

A) True
B) False

75) You can view ……. while working with keyword view.

A) object properties
B) action properties
C) action call properties
D) checkpoint properties
E) Output value properties
F) None of the above
G) All of above

76) You cannot manage some aspects of a local object repository using the QuickTest Object Repository automation object model..

A) True
B) False

77) For each action, you can use a combination of objects from your local and shared object repositories.

A) True
B) False

78) QuickTest adds all new objects to the local object repository even if one or more shared object repositories are already associated with the action assuming that an object with the same description does not already exist in one of the associated shared object repositories..

A) True
B) False

79) If a child object is added to a local object repository, and its parents are in a shared object repository, then you have to manually drag and drop its parent objects from shared object repository to local object repository.

A) True
B) False

80) The ……. is not accessible as a separate file

A) local object repository
B) shared object repository
C) Both
D) None

81) In the Object Repository window:.

A) Local objects are editable (black)
B) Shared objects are in read-only format (gray)
C) Local objects are in read-only format (gray)
D) Shared objects are editable (black)

82) Mark true statement(s):.

A) You can delete objects from a shared object repository using the Object Repository window.
B) You can delete objects from the local object repository using the Object Repository Manager
C) You can delete objects from the local object repository using the Object Repository window
D) You can delete objects from a shared object repository using the Object Repository Manager

83) You can modify an object stored in a shared object repository.

A) using the Object Repository Manager
B) using the Object Repository window
C) you can copy it to the local object repository and then modify its properties
D) you cannot modify properties of objects stored in Shared object repository

84) If an object is contained in both local and shared repositories then, during a run session.

A) QuickTest will use the object in the local object repository
B) QuickTest will use the object in the Shared object repository
C) There will be a conflict
D) QuickTest will use Descriptive Programming

85) When you copy an object to the local object repository

A) its parent objects are also copied to the local object repository
B) its parent objects are not copied to the local object repository
C) You have to manually copy its parent objects are also copied to the local object repository
D) You have to manually drag and drop its parent objects

86) For tests, you can also view test object properties and property values for objects in the Active Screen, regardless of whether the objects are
stored in the object repository.

A) True
B) False

87) Object Properties window differs for objects stored in Shared and Local object repository.

A) True
B) False

88) You can rename objects in the shared object repository using the Object Repository Manager

A) True
B) False, you cannot rename objects in shared object repository

89) When you modify the name of an object in the local object repository, the name is automatically updated in ……. for all occurrences of the object..

A) in the Keyword View
B) in the Expert View
C) Both Keyword and Expert View
D) Changing name of an object doest not effect keyword or expert view

90) When you modify the name of an object in a shared repository, the name is automatically updated in all tests open on the same computer that use the object repository as soon as you make the change, even if you have not yet saved the object repository with your changes.

A) True
B) False

91) An …….. assigns a numerical value to a test object that indicates its order or location relative to other objects with an otherwise identical description (objects that have the same values for all properties)

A) Index identifier.
B) ordinal identifier.
C) SMART ID identifier.
D) original identifier.

92) You can add an object to the local object repository only if that object does not already exist in a shared object repository that is associated with the action. If an object already exists in an associated shared object repository, you can add it to the local object repository using the …….. option.

A) Copy from Shared Repository
B) Copy from Shared Object Repository
C) Copy to Local
D) Copy to Local repository

93) You can copy, paste, and move objects in the local object repository using the Object Repository window, and copy, paste, and move objects both within a shared object repository and between shared object repositories using the Object Repository Manager. But you cannot copy objects from a shared object repository to the local object repository to modify them locally

A) True
B) False

94) At the time of copying, pasting and moving objects, you cannot move an object to any of its descendants.

A) True
B) False

95) When you remove a step from your test, its corresponding object is also removed from the object repository

A) True
B) False

96) You can use the Find and Replace dialog box to replace property or object names.

A) True
B) False

97) The Object Repository window is …… during record and run sessions

A) read-only
B) read-write only
C) read-write and enable
D) None of above

98) In the Associated Repositories tab of the Action Properties dialog box, the ……object repository is always listed first and cannot be moved down the priority list or deleted.

A) local
B) shared
C) Both
D) None

99) In the Associated Repositories tab of the Action Properties dialog box, although we can order the object repositories according to our choice except the fact that Shared Repository remains the first one and cannot be removed.

A) True
B) False

100) If your object repositories are stored in the file system and you want other users or Mercury products to be able to run this action on other computers, you should set the file path as a

A) Absolute path
B) relative path
C) both
D) None of above

101) A test comprises calls to actions. When you create a new test, it contains a call to a …… action.

A) One
B) Two
C) Three
D) Multiple

102) When you open a test, you can choose to view ……

A) the test flow (calls to actions)
B) you can view and edit the individual actions stored with your test.
C) Both A & B
D) None

103) For every action called in your test, QuickTest creates a corresponding …….. in the Data Table so that you can enter Data Table parameters that are specific to that action only.

A) action sheet
B) Excel sheet
C) Both A & B
D) None

104) When you create a test, it includes ….. action.

A) Single
B) unlimited
C) Three
D) Multiple

105) There are three kinds of actions:

A) non-reuse action, reuse action, external action
B) Call to internal action, Call to reusable action, external action
C) non-reusable action, reusable action, external action
D) Call to non-reusable action, reusable action, external action

106) By default, new actions are

A) Short
B) External
C) reusable
D) non-reusable

107) You can display or hide the Action toolbar in the Keyword View by choosing ……..

A) View > Toolbars > Action
B) View > Toolbars > Actions
C) View > Toolbar > Action
D) Views > Toolbars > Action

108) The …… enables you to view either the entire test flow (the calls to the actions in the test) or you can view the steps for a selected reusable or external action.

A) Action Flow
B) Action file
C) Action List
D) Action Repository

109) In the ……., the Action List is always visible and the Expert View always displays the script for the selected action.

A) Keyword View
B) Expert View
C) Action Flow
D) Action View

110) If the action is called more than once within the test flow or if the action is called by a reusable action, the Reusable action option is ……

A) read-only
B) write-only
C) both read and write
D) read-write-executable.

111) You cannot expand …… actions from the test flow view.

A) reusable
B) non-reusable
C) both A & B
D) None

112) You can associate shared object repositories with …… actions simultaneously, using the Associate Repositories dialog box

A) seven
B) Two
C) Three
D) Multiple

113) You can associate ……. object repositories with an action, and the same object repository can be associated with different actions as needed

A) Nine
B) Twenty one
C) as many as you need
D) Twelve

114) Sometimes you may want to call an action from within an action. This is called …….

A) Reusability
B) Nesting
C) Sharing
D) None

115) If a reusable action is called more than once in a test and you split the action into two independent actions, each call to the action within the test will be followed by a call to the new (reusable) action. If a reusable action is called from another test, however, …… it may cause the calling test to fail.

A) Nesting
B) Splitting
C) Reusing
D) Both A & C

116) You must use the …… Action option in QuickTest if you want to save an action under another name.

A) Resave
B) Rename
C) Reuse
D) Split

117) When you remove an external action, you remove all calls and the action from the action list. The original action is also affected.

A) True
B) False

18) You can also press …… to open the Rename Action dialog box

A) Shift + F2
B) Shift + F3
C) Shift + F4
D) Shift + F5

119) If you want to include one or more statements in every new action in your test, you can create an ….

A) reusable action
B) split action
C) Function
D) action template

120) With QuickTest Professional 9.0, a maximum of ………. Actions can be placed into a script

A) 110
B) 256
C) 120
D) 512

121) Only the file name …… is recognized as an action template

A) ActionTemplate.mst
B) Action_Template.mst
C) Action-Template.mst
D) ActionTemplates.mst

122) You can import and export object repositories from and to …. files.

A) XML
B) MTS
C) TSR
D) XLS

123) In general, the ……. object repository is easiest to use when you are creating simple record and run tests.

A) Shared
B) Local
C) Both
D) None

124) The Object Repository automation object model enables you to manipulate QuickTest ……. object repositories and their contents from outside of QuickTest.

A) Shared
B) Local
C) Both
D) None

125) Before using the Object Repository automation object model to manipulate shared object repository stored in Quality Center, you must download the shared object repository and save it to the file system.

A) True
B) False

126) SetTOProperty changes the property values used to identify an object during the test run. It also effects the values saved in the Object Repository for the object.

A) True
B) False

127) After creating or editing an object repository XML file, it is recommended to use the QuickTest ……….functionality to verify that your file conforms to the QuickTest object repository schema.

A) Schema Verification
B) Schema Validation
C) XML Validation
D) XML Verification

128) To display the Comment in the Object Repository dialog box, you must use the attribute name ………

A) miccommentproperty
B) commentproperty
C) mic_comment_property
D) None of above

129) ObjectRepositoryUtil Object Enables you to manipulate …..object repository files from outside of QuickTest Professional.

A) Shared
B) Local
C) Both
D) None

130) You can use the Object Repository Merge Tool to merge objects from ……

A) two shared object repositories into a single shared object repository.
B) the local object repository of one or more actions or components into a shared object repository.
C) Both A & B
D) None

131) GetTOProperty method returns the value of a specified property for a test object from the Object Repository.

A) True
B) False

132) The new Object Repository Comparison Tool is accessible from the Object Repository Manager. You can use this tool to identify the differences between objects in ……..

A) two specified shared object repository files.
B) a Shared and a Local object repository files.
C) either Shared or Local object repository files.
D) two specified Local object repository files.

133) You can use the objects and methods of the QuickTest ……………….. to write scripts that automatically manipulate object repositories, instead of performing these operations manually using the Object Repository Manager.

A) Automation object model
B) Object Repository automation object model
C) Object Repository model
D) Object Repository Script Object model

134) You must convert object repository files from QuickTest Professional 8.2.1 or earlier to the current format before you can use them in QuickTest Professional 9.0 or later. Which method lets you do so.

A) Conversion method
B) Converge method
C) Convert method
D) None

135) You open the Object Repository window for a specific component by choosing ……….

A) Resources > Object Repository
B) Tools > Object Repository
C) File > Object Repository
D) Help > Object Repository

136) In QTP 9 or above, Test objects can be stored in two types of object repositories—……..

A) a shared object repository and a Per-Action object repository.
B) a shared object repository and a local object repository.
C) a shared object repository and a Action object repository.
D) Both A & C

137) The Object Repository Manager enables you to open …… shared object repositories and modify them as needed

A) multiple
B) three
C) two
D) Seven

138) …….. Method Loads the specified object repository.

A) Overload
B) Load
C) Both A & B
D) None

139) An object repository that is currently open by another user is locked, is it possible to merge a locked object repository.

A) Yes
B) No

140) You can manage the shared object repository associations of a selected test using the …………

A) Associate Repositories dialog box
B) Object Repositories dialog box
C) Associate Repositories Manager dialog box
D) Object Repositories Manager dialog box

141) All changes you make to an object repository are automatically updated in all components open on the same computer that use the object repository as soon as you make the change—even if you have not yet saved the object repository with your changes.

A) True
B) False

142) If you want to modify an object stored in a shared object repository, you can modify it…….

A) using the Object Repository Manager
B) you can modify it locally using the Object Repository window.
C) Both A & B
D) None of above

143) ……………. Returns an ObjectRepositories collection representing all object repository files associated with the action.

A) Object Property
B) Automation Object Model
C) ObjectRepositories Property
D) OR Property

144)
If you do not want QuickTest to perform a step or checkpoint until an object in your application achieves a certain status, you should insert a ………. point to instruct QuickTest to pause the test until the object property achieves the value you specify

A) Synchronization
B) Check
C) Smart Identification
D) none of above

145)
Where do we Specify the Maximum Time to Wait for a Web Page to Load

A) File->Settings, Web Tab.
B) Tools->Options, Web Tab.
C) Resources->Settings, Web Tab
D) None of above

146)
You can insert …….. statements that instruct QuickTest to wait until an object exists

A) Exist
B) Wait
C) Both A & B
D) None

147)
…… Method Waits for the browser to complete the current navigation.

A) Exist
B) Wait
C) WaitProperty
D) Sync

148)
Sub Sync_Example()
Browser(“Mercury Tours”).Page(“Mercury Tours”).Sync
End Sub

The above example uses the Sync method to wait for the Mercury Tours page to synchronize before performing the next operation.

A) True
B) False

149)
…..Property- The period of time QuickTest waits before checking the emulator status (in milliseconds).

A) SyncTime
B) Sync.Time
C) TimeSync
D) Time.Sync

150)
……. Property- Indicates whether QuickTest beeps after performing each Sync function during a run session.

A) BeepAfterSync
B) BeepOnSync
C) BeepSync
D) Beep.Sync

151)
Unlike the Exist method, the ……. method enables you to synchronize the test run based on a specific object property.

A) WaitProperty
B) Wait
C) Sync
D) Exit

152)
…… Statement – Initiates a pause during a run session.

A) WaitProperty
B) Wait
C) Sync
D) Exit

153)
……….. Property – The maximum time (in milliseconds) that QuickTest waits for a Web page to load before running a step.

A) BrowserTimeout
B) Browser_Navigation_Timeout
C) BrowserNavigationTimeout
D) Browser_Timeout

154)
The …….. checks a variety of objects such as buttons, radio buttons, combo boxes, lists, and so forth.

A) Image checkpoint
B) standard checkpoint
C) Bitmap checkpoint
D) Accessibility checkpoint

155)
You create an image checkpoint by inserting a …….. on an image object.

A) Image checkpoint
B) standard checkpoint
C) Bitmap checkpoint
D) Accessibility checkpoint

156)
……… are also supported for some list view objects, such as WinListView and VbListView, as well as other list view objects in external add-in environments.

A) Table checkpoints
B) standard checkpoints
C) Accessibility checkpoints
D) XML checkpoints

157)
…….identifies areas of your Web site that may not conform to the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines.

A) Accessibility Checkpoint
B) standard checkpoints
C) Database checkpoints
D) Accessible Checkpoint

158)
…….. Specifies the time interval (in seconds) during which QuickTest attempts to perform the checkpoint successfully.

A) Check timeout
B) Checkpoint interval timeout
C) Checkpoint timeout
D) Quicktest timeout

159)
……….. Specifies when to perform the checkpoint in the test.

A) Insert statement.
B) Check statement.
C) timeout statement.
D) checkpoint statement.

160)
You can view the results of the checkpoint in the ……..

A) Test Results window
B) Checkpoint window
C) Information Pane
D) Checklist window

161)
By default, the bottom right part of the Test Results window displays information on the selected checkpoint only if it has the status Failed.

A) True
B) False

162)
You can also use the ……… to check specific property values.

A) CheckProperty method
B) CheckItemProperty method
C) ItemProperty method
D) Property method

163)
If you want to retrieve the return value of a checkpoint (a boolean value that indicates whether the checkpoint passed or failed), you must add ……… the checkpoint argument in the statement in the Expert View.

A) parentheses around
B) Properties with
C) Arguments with
D) Values alongwith

164)
You can use a formula in a checkpoint to confirm that an object created on-the-fly (dynamically generated) or another variable object in your Web page or application contains the value it should for a given context.

A) True
B) False

165)
You cannot modify the settings of existing checkpoints.

A) True
B) False

166) You can edit information in the Data Table by typing directly into the table cells.

A) True
B) False

167) Each row in the table represents the set of values that QuickTest submits for the ……… arguments during a single iteration of the test or action.

A) parameterized
B) Non-parameterized
C) distributed
D) None of above

168) For every action called in your test, QuickTest creates a corresponding …….. in the Data Table so that you can enter Data Table parameters that are specific to that action only.

A) action sheet
B) Excel sheet
C) Both A & B
D) None

169) When you create a test, it includes ….. action.

A) Single
B) unlimited
C) Three
D) Multiple

170) There are three kinds of actions:

171) By default, new actions are

A) Short
B) External
C) reusable
D) non-reusable

172) You can display or hide the Action toolbar in the Keyword View by choosing View > Toolbars > Action.

A) View > Toolbars > Action
B) View > Toolbars > Actions
C) View > Toolbar > Action
D) Views > Toolbars > Action

173) The …… enables you to view either the entire test flow (the calls to the actions in the test) or you can view the steps for a selected reusable or external action.

A) Action Flow
B) Action file
C) Action List
D) Action Repository

174) In the ……., the Action List is always visible and the Expert View always displays the script for the selected action.

A) Keyword View
B) Expert View
C) Action Flow
D) Action View

175) ……. Method – Imports a sheet of a specified file to a specified sheet in the run-time Data Table.

A) SheetImport
B) ImportSheet
C) ImportDataTable
D) ImportTable

176) The column headings in the sheet you import must match the Data Table parameter names in the action for which the sheet is being imported. Otherwise, your test or component may fail.

A) True
B) False

177) The sheet you import automatically takes the name of the sheet it replaces.

A) True
B) False

178) The use of complex and/or nested formulas in the Data Table is supported.

A) True
B) False

179) The data your test uses is stored in the ……. Data Table, which is displayed in the Data Table pane at the bottom of the screen while you insert and edit steps.

A) design-time
B) Run-time
C) Current
D) None

180) During the run session, QuickTest creates a ……. Data Table—a live version of the Data Table associated with your test.

A) True
B) False

181) If it is important for you to save the resulting data from the run-time Data Table, you can insert a ……….statement to the end of your test to export the run-time Data Table to a file.

A) Export.Datatable
B) DataTable_Export
C) DataTable.Export
D) Both A & B

182) When you parameterize a step in a test using the Data Table, you must decide whether you want to make it a global Data Table parameter or an action Data Table parameter.

A) True
B) False

183) After running a parameterized test, you can view the actual values taken from the Data Table in the Test Results Run-Time Data Table.

A) True
B) False

184) …… Property – Returns the design-time Data Table, which enables you to modify the data that is used for the Data Table parameters in your test or business component.

A) DataTable
B) DesignTable
C) Design_Table
D) None

185) The Data Table assists you in parameterizing your test.

A) True
B) False

16:–

1) Programmatic description can be very useful if you want to perform an operation on an object that is stored in the object repository.

A) True
B) False

2) There are two types of programmatic descriptions:

A) Static & Dynamic
B) Statement & Dynamic
C) Step & Dynamic
D) Standard & Dynamic

3) You can also use programmatic descriptions to perform the same operation on several objects with certain identical properties, or to perform an operation on an object whose properties match a description that you determine dynamically during the run session.

A) True
B) False

4) QuickTest evaluates all property values in programmatic descriptions as regular expressions

A) True
B) False

5) From the below 4 statements which one is invalid:

A) Browser(“Title:=Mercury Tours”).Page(“Title:=Mercury Tours”).WebEdit(“Name:=Author”, “Index:=3″).Set “Amit Kumar”
B) Browser(“Index”).Page(Desc1).Link(docu3)
C) Browser(“Mercury Tours”).Page(“Title:=Mercury Tours”).WebEdit(“Name:=Author”, “Index:=3″).Set “Amit Kumar”
D) Browser(“Title:=Mercury Tours”).Page(“Title:=Mercury Tours”).WebEdit(“Author”).Set “Amit Kumar”

6) When using programmatic descriptions from a specific point within a test object hierarchy, you must continue to use programmatic descriptions from that point onward within the same statement.

A) True
B) False

7) You can run any application from a specified location using a ….. statement.

A) Start.Application
B) System.UtilRun
C) SystemUtil.Run
D) SystemUtii.RUn

When creating a programmatic description for an ActiveX test object and the relevant run-time object is windowless (has no window handle associated with it), you must add the …….. property to the description and set its value to True.

A) Window Handle
B) WindowLess
C) Winless
D) None

9) You can compare the run-time value of a specified object property with the expected value of that property using either programmatic descriptions or user-defined functions.

A) True
B) False

10) When you specify an application to open using the Record and Run Settings dialog box, QuickTest adds a SystemUtil.Run statement to your test.

A) True
B) False

17:–

1) You can use the Expert View tab to view a text-based version of your test.

A) True
B) False

2) Expert View contains each step as a VBScript line. In object-based steps, the VBScript line defines the …….. hierarchy.

A) Action
B) Object
C) Test
D) Step

3) If you focus on a specific step in the Keyword View and switch to the Expert View, the cursor is located in that ….. line of the test.

A) Next
B) Previous
C) Last
D) Corresponding

4) For each object and method in an Expert View statement, a corresponding row exists in the Keyword View.

A) True
B) False

5) When you switch from the Expert View to the Keyword View, QuickTest automatically checks for syntax errors in your script, and shows them in the Information pane.

A) True
B) False

6) In the Expert View, the ……. is always visible and the Expert View always displays the script for the selected action.

A) Action List
B) Expert List
C) Check List
D) View List

7) You can insert a checkpoint or output value statement in the Expert View manually.

A) True
B) False

You can copy a Checkpoint or Output statement from the Expert View to another test.

A) True
B) False

9) You can also manually enter standard VBScript statements, as well as statements using QuickTest test objects and methods, in the Expert View.

A) True
B) False

10) You cannot print the test displayed in the Expert View or a function library.

A) True
B) False

11) When you type in the Expert View or a function library, ………. enables you to select the test object, method, property, or collection for your statement from a drop-down list and view the relevant syntax.

A) Object Property dialog box
B) Web edit Property dialog box
C) Intellisense
D) dropdown list

18:–

1)
Using QuickTest, you can define and store your user-defined functions in a …..

A) function library
B) directly in an action within a test.
C) both A & B
D) None

2)
Default file extention of function library is

A) .flf
B) .qtfl
C) .qfl
D) .tfl

3)
When you store a function in a test action, it can be called from any other action or test.

A) True
B) False

4)
You cannot define private functions and store them in a function library.

A) True
B) False

5)
You can drag and drop a function (or part of it) from one document to another.

A) True
B) False

6)
You can add steps to your function library manually or using the Step Generator.

A) Manually
B) using Step Generator
C) Both A & B
D) None

7)
In function libraries, IntelliSense does not enable you to view test object names or collections because function libraries are not connected to object repositories.

A) True
B) False

Function Libraries can be edited during the debug session.

A) True
B) False

9)
To close all open function libraries:

A) Choose File > Close All Function Libraries,
B) Window > Close All Function Libraries.
C) Widow > Close All
D) Both A & B

10)
Any text file written in standard VBScript syntax can be used as a function library.

A) True
B) False

11)
If you create a user-defined function manually and do not define the scope as Public or Private, it will be treated as a ….. function, by default.

A) Private
B) Public
C) Both A & B
D) None

12)
If you choose not to register your function at this time, you can manually register it later by adding a RegisterUserFunc statement after your function

A) RegisterUserFunction
B) RegisterUserFunc
C) RegUserFunc
D) Both A & B

19:—

1)
You can parameterize values ….. in your test.

A) in Steps
B) in Checkpoints
C) of Action Parameters
D) Both A & B
E) All of above

2)
You can parameterize values in steps and checkpoints while …… your test.

A) recording
B) editing
C) Both A & B

3)
There are four types of parameters: Test/Action, Random number, Environment Variable, Regular Expression.

A) True
B) False

4)
While using Test and Action Input Parameters,you can enter the parameter name in the Expert View using the Parameter utility object, in the format: ………… for the current action.

A) Parameter(“ParameterName”)
B) ParameterName(“Parameter”)
C) Parameter(“Parameter-Name”)
D) Parameter(“Parameter_Name”)

5)
….. parameters are available only for top-level actions.

A) Action
B) Environment Variable
C) Test
D) None

6)
…… parameters are available for subsequent steps and for nested actions. They are defined in the action containing the steps or in the action that calls the nested action.

A) Action
B) Environment Variable
C) Test
D) Parent action

7)
When specifying the name for data table parameter, the first character of the parameter name must be a ……

A) letter
B) underscore
C) number
D) both A & b

By outputting values to the global Data Table sheet from one action and using them as input parameters in another action, you can easily pass values from one action to another.

A) True
B) False

9)
……. parameters are especially useful for localization testing, when you want to test an application where the user interface strings change, depending on the selected language.

A) Action
B) Environment
C) Test
D) Parent action

10)
You can also store environment variable files in Quality Center.

A) True
B) False

11)
……. built-in environment variable that tells version of the OS on which you are working.

A) OS
B) OS_Ver
C) OSVER
D) OSVersion

12)
Random number parameters are appropriate for non-numeric
values, such as text or hypertext links.

A) True
B) False

20:–

1)
Regular expressions enable QuickTest to identify objects and text strings with undependable values.

A) True
B) False

2)
You can use regular expressions only for values of type string and number.

A) True
B) False

3)
If you expect the value of a property to change in an unpredictable way during each run session, you can use regular expressions

A) True
B) False

4)
All …….. are automatically treated as regular expressions.

A) programmatic description
B) Window
C) WinObject
D) Collection

5)
If a backslash character is used before a character that has no special meaning, the backslash is ignored.

A) True
B) False

6)
You can use regular expressions in the Find what and Replace with strings to enhance your search.

A) True
B) False

7)
Regular Expressions can also be used with XML checkpoints.

A) True
B) False

What is the Regular Expression Matching Zero or More Specific Characters

A) x
B) #
C) *
D) &

21:–

1)
Virtual objects enable you to record and run tests on objects that are normally recognized by QuickTest.

A) True
B) False

2)
In the test results, the virtual object is displayed as though it is a standard class object.

A) True
B) False

3)
QuickTest does not support virtual objects for ……. recording.

A) analog
B) low-level
C) normal
D) both A & B
E) both A & C

4)
You can use the Object Spy to view virtual object properties.

A) True
B) False

5)
You cannot insert any type of checkpoint on a virtual object

A) True
B) False

6)
The ………… contains all the virtual object collections defined on your computer.

A) Virtual Objects Manager
B) Virtual Manager
C) Virtual Object Manager
D) Virtual Object Wizard

7)
Extention of virtual object collection files

A) .vcf
B) .vot
C) .vct
D) .vcd

You can remove virtual objects from your test by ……. these objects.

A) disabling recognition of
B) deleting
C) deleting virtual object collection files of
D) All of Above
E) both A & B

9)
When you want QuickTest to recognize virtual objects during recording, ensure that the ……. check box in the General tab of the Options dialog box is cleared.

A) Disable recognition of virtual object Files while recording
B) Disable recognition of virtual object Collection while recording
C) Disable recognition of virtual objects while recording
D) Enable recognition of virtual objects while recording

10)
QuickTest identifies a virtual object according to its ……

A) Properties
B) boundaries
C) Object Spy
D) Edges

22:-

1)
Recovery scenarios activate specific recovery operations when ……… occur.

A) Specific Errors
B) Test Errors
C) Trigger Events
D) QTP Errors

2)
You can also control and activate your recovery scenarios during the run session by inserting ………….. into your test.

A) Trigger Events
B) Recovery Events
C) Recovery Statements
D) Catch Statements

3)
If you choose On error in the Activate recovery scenarios box in the Recovery tab of the Test Settings dialog box, the recovery mechanism does not handle triggers that occur in the last step of a test.

A) True
B) False

4)
By default, recovery scenario operations are activated only after a step returns an error.

A) True
B) False

5)
A ……. is a convenient way to organize and store multiple recovery scenarios together.

A) recovery file
B) recovery folder
C) Recovery Log
D) Log File

6)
The Recovery Scenario Manager dialog box enables you to create and edit recovery files, and does not let you create and manage the recovery scenarios stored in those files.

A) True
B) False

7)
Each recovery scenario is represented by an icon that indicates its type.

A) True
B) False

The Recovery Operations screen in Recovery Scenario Wizard enables you to manage the collection of …….. in the recovery scenario.

A) recovery operations
B) recovery Files
C) Trigger events
D) All of Above

9)
If you define a Restart Microsoft Windows recovery operation, it is always inserted as the last recovery operation, and you can change its position in the list.

A) True
B) False

10)
If more than one scenario uses a function with the same name from different function libraries, the recovery process may fail.

A) True
B) False

(0) Comments Read More

Jul

Posted on 06-07-2010

Risk Analysis in Software Testing

Filed Under (Software Testing) by Sathesh on 06-07-2010

A risk is a potential for loss or damage to an Organization from materialized threats. Risk Analysis attempts to identify all the risks and then quantify the severity of the risks.A threat as we have seen is a possible damaging event. If it occurs, it exploits vulnerability in the security of a computer based system.

Risk Identification:

1. Software Risks: Knowledge of the most common risks associated with Software development, and the platform you are working on.

2. Business Risks: Most common risks associated with the business using the Software

3. Testing Risks: Knowledge of the most common risks associated with Software Testing for the platform you are working on, tools being used, and test methods being applied.

4. Premature Release Risk: Ability to determine the risk associated with releasing unsatisfactory or untested Software Prodicts.

5. Risk Methods: Strategies and approaches for identifying risks or problems associated with implementing and operating information technology, products and process; assessing their likelihood, and initiating strategies to test those risks.

Traceability means that you would like to be able to trace back and forth how and where any work product fulfills the directions of the preceding (source-) product. The matrix deals with the where, while the how you have to do yourself, once you know the where.

Take e.g. the Requirement of User Friendliness (UF). Since UF is a complex concept, it is not solved by just one design-solution and it is not solved by one line of code. Many partial design-solutions may contribute to this Requirement and many groups of lines of code may contribute to it.

A Requirements-Design Traceability Matrix puts on one side (e.g. left) the sub-requirements that together are supposed to solve the UF requirement, along with other (sub-)requirements. On the other side (e.g. top) you specify all design solutions. Now you can connect on the crosspoints of the matrix, which design solutions solve (more, or less) any requirement. If a design solution does not solve any requirement, it should be deleted, as it is of no value.

Having this matrix, you can check whether any requirement has at least one design solution and by checking the solution(s) you may see whether the requirement is sufficiently solved by this (or the set of) connected design(s).

If you have to change any requirement, you can see which designs are affected. And if you change any design, you can check which requirements may be affected and see what the impact is.

In a Design-Code Traceability Matrix you can do the same to keep trace of how and which code solves a particular design and how changes in design or code affect each other.

Demonstrates that the implemented system meets the user requirements.

Serves as a single source for tracking purposes.

Identifies gaps in the design and testing.

Prevents delays in the project timeline, which can be brought about by having to backtrack to fill the gaps.

Risk analysis is appropriate to most software development projects.

Use risk analysis to determine where testing should be focused:

1. Which functionality is most important to project

2. Which functionality is most visible to user

3. Which functionality has largest impact on users.

4. Which aspects of the application is most important to the customer

5. Which aspects of the application is tested early in the development cycle.

These are some of the risk analysis factors to test an application.

The two most important characteristics of Risks are
a. Its Adverse effect to the success of the project
b. Its uncertainty.

Typical parameters used in analysis of risks are
1. Probability of occurrence
2. Impact of the risk – this is sometimes a product of Severity of the impact and period in which the risk might occur.

The product of the above two parameters will give you Risk Exposure factor based on which the the priority of the risks to be mitigated or acted upon could be decide.

Risks are always as against the business requirements for which the software has been created. So, it is always very important to understand the risks that can affect the client’s business and its impact. Testers need inputs from client as well as developers with regard to this understanding. What you may consider as risk from testing point of view may not be as seen by the client. So, it is necessary to associate risk level with each requirement and also the priority. This will be very beneficial while suggesting go/no go for production.

(1) Comment Read More

Jul

Posted on 04-07-2010

The One-Hour Regression Test

Filed Under (Regression testing) by Sathesh on 04-07-2010

The One-Hour Regression Test

Software regression testing is an essential and challenging task for software test groups. By definition, regression testing is the process of verifying that none of the existing system features have been accidentally broken by any new features or recent bug fixes. The main challenges for regression testing are performing as many tests as possible in as short a time as possible and finding any serious regression defects as early as possible in the regression test cycle.

The classical regression test cycle is:

A final software version with all of the new features completed and with all of the major bugs fixed becomes available from the software development team.
Functional tests (for new features) and regression tests (for existing features) are executed.
Performance, integration, interoperability, and stress tests are executed.
If any serious defects are found, or significant feature changes are needed, steps 1 through 3 are repeated.
When all needed features are operational and no major defects remain, the software is released from test, ready for customer use.

Problems Inherent in Regression Testing
Although it is easy to follow this sequence, there are several problems with this classical approach to regression testing.

Lather-rinse-repeat
The goal of regression testing is to find problems in previously working software features. Although project management may choose to defer fixes or, in some cases, not to fix problems at all, there will be some defects found during regression testing that must be fixed before release. Then the fix-regression test cycle repeats itself, perhaps many more times than the schedule allows.

Any code change can break anything and everything
Project managers often believe that any defects introduced by a code change will be isolated to that particular area of the code and, thus, an abbreviated regression test focused on that particular feature area is sufficient. Eventually you learn that any code change–no matter how isolated–can have indirect, inadvertent, and catastrophic effects on seemingly unrelated areas of the code. Sometimes a bug lies latent in the code for years until some other change is made, which at last reveals the bug.

The best tests are often saved for last
Most regression test plans are arranged in a logical order that starts with some simple tests, such as “ping the server;” proceeds through the multiple functionalities of the product; and ends with complex performance tests, such as “measure the routing convergence time with one million routes in the table.” Although logical from a tester’ perspective, it is completely backwards from the regression test’s goal of finding the most serious defects first. The tests that are the most complex, the most demanding, and the most critical for product and customer success should be executed first.

Getting meaningful results is slow
Both automated and manual approaches to regression testing tend to take a day or more before we know if the latest software version is acceptable or if it has serious problems. More complex performance, interoperability, and stress tests can take weeks to perform. But managers may need to know within hours if the latest version is good enough for a customer demonstration of a new feature or if it fixes a critical issue being experienced at a customer site without introducing any new problems.

Regression testing is repetitious, dull, and tedious
Regression testing tends to be the least favorite activity for software testers due to its repetitive nature. After a few iterations, the same manual tests become mind numbing, especially if few regression bugs are found. Automated test scripts are usually developed to speed up regression testing and reduce the burden on human testers. But, multiply a simple automated regression test by the thousands of features that exist in most products and the result is tens of thousands of lines of regression test scripts to maintain–another dull task.

Regression testing is a major resource drain
Most test groups dedicate the majority of their resources to regression testing, either by writing and maintaining thousands of automated tests or by having a large number of testers spend weeks performing the regression testing manually. As problems are found in the software, the test team becomes trapped in an endless repetition of the regression test cycle, never able to escape in order to spend adequate time working on new feature tests or better tests.

Attempts to Deal with These Problems
Many test groups have tried to deal with the problems of classical regression testing by using one of these four approaches:

The complete regression test
Some test groups seek to avoid regression m test problems by starting regression testing on one software version and continuing for days or weeks on that same version until the regression tests are completed, even though newer software versions are becoming available during the regression test cycle. These versions remain untested until the current regression test cycle is completed, but then regression testing starts again on the latest version.

The continuous regression test
Other test groups seek to avoid the problems by accepting new software versions on a daily or weekly basis during the regression test cycle. When a new version is available, it is loaded onto the test systems and testing continues without restarting. At the end of testing, the regression tests have been spread across multiple software versions. No version has been completely tested, but the regression test has been run only once.

The regression smoke test
Other test groups scale back the scope of regression testing so that a superficial, usually automated, “smoke test” can be completed within a few hours on each new software version. Full regression testing is done only on the “final” version.

The restartable regression test
Other groups restart regression testing as each new version of software becomes available, particularly if it is toward the end of the release schedule and there is a belief that this is the final (or nearly final) version that will need to be tested. Of course, any serious problems that are found require regression testing to restart (again). And rarely does the schedule clock restart to allow enough time to perform a full regression test. Sometimes the first test cases will get executed over and over for each software version, while test cases toward the end of the test plan may get executed only once.

Still, the Problems Remain
Each of these approaches to regression testing results in little meaningful testing being performed on the last software version. This lack of meaningful testing fails the purpose of regression testing, which is to give, in a timely manner, high confidence that all critical features are still working.

A common approach to mitigate the risk of performing very little regression testing is to perform a more comprehensive test on the “final” version. The problem with this is that it is impossible to know before regression testing starts that the “final” testing won’t find any major problems and require yet another final version to be built and tested comprehensively, followed by another final version, and so on.

The One-Hour Regression Test Strategy
These problems can be minimized by the adoption of a “one-hour regression test” strategy. This strategy:

Attempts to find the most serious bugs as quickly as possible, at the cost of finding the lesser issues later in the regression test cycle
Adapts to the various styles of regression testing: the complete regression test, the continuous regression test, the regression smoke test, and the restartable regression test
Does not require additional people, test equipment, or weekend work

Ask Yourself, “What if I only had an Hour?”
What if a customer asked you to demonstrate to him, within an hour, that your newest software is ready for use? What tests would you run? Now, think carefully–are these the same tests that you are now performing in your first hour of regression testing?

The importance of the first hour
“Wait a minute,” you say. “I have six weeks to execute my regression test plan. Is the first hour really that important?”

In a word, yes. Finding the biggest problems as early as possible in the regression test cycle gives the development team the maximum time to develop a comprehensive fix–not just a quick fix.

Immediate feedback on the software quality keeps the entire project team focused on the goal at hand, which is to produce high-quality software as quickly as possible. In addition, immediate feedback prevents other projects from diverting (stealing) your development resources.

Immediate feedback gives project management the maximum amount of time to react to problems. Sometimes it is necessary to reset (lower) customer expectations. Knowing this as soon as possible makes a difficult job easier.

Immediate feedback gives the test team greater awareness of where the problem areas are in the current software version. This guides testers to avoid further testing of that feature until it is fixed and then to perform additional testing of that feature after it is fixed.

Declaring the latest version “dead on arrival” can take pressure off the test team. Instead of spending several days performing low-value tests that will have to be repeated anyway, you can spend the bulk of your time performing, automating, and improving interesting, high-value regression tests.

How to pick the right tests for the first hour
The philosophy of one-hour regression testing is very different from the philosophy of classical regression testing. Instead of methodically validating that each and every feature meets the requirements of the product specification, the first-hour test approach tries to find the major problems with the version as quickly as possible.

The right regression tests to perform in the first hour will vary depending on the type of product, the maturity and stability of the software, and the test resources available. The following questions will help you select the right first-hour tests for your product.

Customer-Focused Tests
First, consider the typical use of the product from beginning to end and make sure that use is tested. Think of global, macroscopic tests of your product. What tests would be the most meaningful to your customers? How does the product fit into the customer’s overall situation and expectation? What is the name of your product? The first tests should make sure that the product lives up to its name. Which features would have the greatest impact on the customer if they were broken? If stored data were lost? If security were compromised? If service were unavailable? These critical features must be tested in the first hour.

Complex and Difficult Tests
Which one usage scenario would tell you that the greatest number of important features is working? Make sure the scenario is a realistic, customer-based configuration. If there is no single scenario, then test your top-three customer usage scenarios that have a lot of “moving parts.” Consider which top-level tests would reveal any problems with numerous underlying unit or feature tests. Which features can be tested together? Instead of regression testing features in isolation, use a real-world mix of compatible features, validating all simultaneously. Finally, what features are the most complex? Which uses are the most dynamic or the most challenging? What tests are the most difficult to pass or have the least margin to spare?

Big Picture Tests
Now step back and look at the big picture. Make sure that you test the overall system performance in large-scale use. What are the important top-level performance metrics? What performance tests can be used as benchmarks of major features? Which tests will quickly show any memory, CPU, or other resource-depletion issues? What tests can indicate overall system health with a busy system?

Expected Failure Tests
What features have historically been a problem for your product? Where have prior defects been found and fixed? These are areas that should be regression tested early in the cycle. Which regression tests are most likely to fail based on the changes that have been made? Use your testing experience and intuition to select the regression tests that have the highest likelihood of failing. What are the newest features in the regression test cycle? These often have problems that slipped past the new feature testing.

The overall goal is to test the software version as deeply and quickly as possible. These tests may take more than an hour, but try to prioritize and select the tests that will provide the most essential information about the quality of the software version within a matter of a few hours.

Putting It All Together
Before starting any regression testing, it is critical to test the bug fixes, new features, or other substantial modifications to existing features that are in this latest version. These changes are the whole reason for building the version; if they aren’t right, you know there will be another build.

Insert the one-hour regression test before your full regression testing but after testing the new features, as follows:

Test the reasons for the build.

Test the bug fixes and test for any likely problems introduced by the fixes.
Test any new features using a “one-hour new-feature test plan.”

Perform your one-hour regression test.

Select performance, load, and capacity tests.
Select interoperability and compatibility tests.
Select database backup and restore tests.
Select redundancy tests, security tests, and data integrity tests.
Select feature and functional tests.

Continue regression testing.

Run any smoke or sanity tests.
Perform load, capacity, interoperability, and performance testing.
Perform stress, fault insertion, endurance, and longevity testing.
Perform detailed tests of each feature, per classical regression testing.

Continuously optimize your first-hour regression testing as bugs are found, new features are added, and testing tools are improved.

Evaluate your current regression test strategy
Now that you have a select list of candidate first-hour tests, compare it with the tests that you are currently performing in the first hour of regression testing. Is your existing regression test plan written in a test-centric or customer- centric sequence? Your first tests should be focused on the complex, large-scale, customer-usage scenarios.

Is your existing regression test plan aging or up to date? Is it constantly updated to integrate the new feature tests into the regression test plan? Or are new feature tests simply tacked on to the end of the test plan, waiting until the end to be executed?

After focusing on the first hour, ask yourself what you want to accomplish in the first four hours, the first eight hours, and the first week. Make sure that you prioritize and rearrange your test cases so that if you are asked to release a version a few days before all of the regression test cases can be completed, all of the critical tests will already have been performed.

Smoke and sanity tests
This one-hour regression test has similarities with two other types of regression testing, smoke testing and sanity testing, but they are very different.

Smoke testing usually refers to superficial tests of the software, such as:

Does the software install and run?
Are all of the screens and menus accessible?
Can all of the objects be accessed?

The one-hour regression test approach is more focused and does not replace the broader smoke test. If possible, the smoke test should be run in parallel with the one-hour regression test. If this is not possible, then run the smoke test immediately after the one-hour regression test.

Sanity testing usually refers to a small set of simple tests that verify basic functionality of the software, such as:

Simple calculations provide correct results.
Basic functions work correctly.
Individual, isolated features work correctly.

There is typically no capacity, scale, or performance testing involved with sanity testing. Sanity testing provides the starting point for in-depth regression testing of each feature. Sanity testing should be performed only after the one-hour regression test is complete. Ideally, sanity tests should be re-examined to provide greater benefit to the regression testing, once the one-hour regression tests are in place.

The one-hour regression test differs from smoke and sanity testing in another important way. The goal of one-hour regression testing is to find the major problems as quickly as possible by testing complex features deeply.

New features
If there are any new features introduced during the regression test cycle, hit them hard in the first hour, shaking out any major design problems. After the new features survive this testing, methodically test the details of the new features using the full new-feature test plan.

Summary
The one-hour regression testing approach performs a small number of the most important and most complex tests during the first hour after each new software version is received, with the goal of finding the big problems early in the regression test cycle.

The various approaches to software testing can all benefit from one-hour regression testing, whether your test group uses a traditional, agile, context-driven, or exploratory test strategy.

The one-hour regression testing approach requires a slight change of thinking for the first hour, but it can save days or weeks of repetitious regression testing, while increasing the overall software quality of your product. {end}

(0) Comments Read More

Jul

Posted on 02-07-2010

Estimating Software Testing Time

Filed Under (Software Testing) by Sathesh on 02-07-2010

A very simplistic method for estimating testing time can be as follows for a typical black box testing assignment .

Total Time=No of cycles*(Time for each testing cycle+time for fixing of bugs found in one cycle)

so if you have an estimated time of testing cycle as 6 days and you expect that the developers are going to take 4 days for fixing bugs found in one cycle and if the number of testing cycles are estimated as 4 then
Total time = 4*( 6+4)
Total time= 40 days

But this is very simplistic model but is useful for simpler projects.

A little more complex model for estimating software testing time involves:
1 Categorizing Software Requirements resulting into number of requirements-they can cover business,technical,functional and performance

2 Using a Complexity Constant ( e.g 1 for simple and 1.5 for complex)
3 Applying Risk Factors (e.g ranging from 1.1 to 1.5)
4 Applying a General Contingency Factor (e.g 1.15-1.35)

so one cycle time =No of requirement*complexity constant*risk factor*contingency factor

If you are implementing the above methods, the you need to consider some other factors also:
When you run test estimation, you can estimate efforts for tasks belong to the Test Team. You cannot figure out a correct estimation for tasks which much depend on developers such as builds release for testing and bug fixing. Normally Builds are released very late to testers and testers have to change their schedule. In addition, Testers do not know and control how bugs are fixed. That is why the hardest part of test estimation is from test execution phase.

The best way to calculate test efforts is you should know how to size projects with function point approach. However, it is not easy task either.

Function point approach is not easy to explain in a post. Let me know if you want to talk more about this.

(0) Comments Read More

May

Posted on 20-05-2010

The Need for Testing

Filed Under (Software Testing) by Sathesh on 20-05-2010

Software development involves ambiguity, assumptions and ﬂawed human communication. Each change made to a piece of software, each new piece of functionality, each attempt to ﬁx a defect, introduces the possibility of error. With each error, the risk that the software will not fulﬁl its intended purpose increases.

Testing reduces that risk. We can use QA processes to attempt to prevent defects from entering software but the only thing we can do to reduce the number of errors already present is to test it. By following a cycle of testing and rectiﬁcation we can identify issues and resolve them.
Testing also helps us quantify the risk in an untried piece of software. After modiﬁcations have been made, a piece of software can be run in a controlled environment and its behavior observed. This provides evidence which informs the decision to move to the next phase of the project or to attempt to rectify the problem.

And ﬁnally in some (dare I say enlightened?) software development efforts, testing can actually be used to drive development. By following statistical models of software development and methods such as usability testing, software development can move from an unfocused artistic endeavor to a structured discipline.

My favorite quote on software, from Bruce Sterling’s “The Hacker Crackdown”

The stuff we call “software” is not like anything that human society is used to thinking about. Software is something like a machine, and something like mathematics, and something like language, and something like thought, and art, and information…. but software is not in fact any of those other things. The protean quality of software is one of the great sources of its fascination. It also makes software very powerful, very subtle, very unpredictable, and very risky.
Some software is bad and buggy. Some is “robust,” even “bulletproof.” The best software is that which has been tested by thousands of users under thousands of different conditions, over years. It is then known as “stable.” This does NOT mean that the software is now ﬂawless, free of bugs. It generally means that there are plenty of bugs in it, but the bugs are well-identiﬁed and fairly well understood.
There is simply no way to assure that software is free of ﬂaws. Though software is mathematical in nature, it cannot by “proven” like a mathematical theorem; software is more like language, with inherent ambiguities, with different deﬁnitions, different assumptions, different levels of meaning that can conﬂict. ”

(0) Comments Read More

QTP Question 04: How Does Run time data (Parameterization) is handled in QTP?

Calender

Archives

Categories

Meta

Pages

StatCounter

Alexa

Blogroll

QTP Question 04: How Does Run time data (Parameterization) is handled in QTP?

Calender

Archives

Tag Cloud

Categories

Meta

Pages

StatCounter

Alexa

Blogroll