QTP Virtual Objects

Most of QTP users are very familiar with Virtual Objects because it solves unrecognized application objects problem. Sometime we work with those applications that have different types of objects but tool does not recognize and support those objects as object. So for this kind of problem every successful tool provides the facility to recognize those objects as Virtual Object.

QTP tool is also providing same and easy steps to define the Virtual Object. Basically we used Virtual object functionality when tool does not support any application object as object.

As we discussing Virtual Object in respect to QTP tool, there some important points which should get the notice by every QTP users.

Point 1: Define the Virtual Object size and position in the web page by using the crosshairs pointer.

Point 2: During a run session make sure that application window should come in same size and same location. May be it effect the coordinates of virtual object.

Point 3: We can not insert any checkpoints for virtual object.

Point 4: We can not use Object Spy for virtual Object.

Point 5: We can use Virtual Object only in recording and running session.

Point 6: Virtual objects store in the computer, not only for current test.

Point 7: We can define the virtual object only for those object in which, we can click or double click.

We can see the all defined virtual objects with the help of Virtual Object Manager window. Basically it list out the all created virtual objects. We can delete or disable the objects with the help of Virtual Object Manager and Options windows. Virtual Object Manager window provide the facility to delete the objects after selecting them and if you want tool should keep the objects but don’t recognize, for that you have to check the option “Disable recognition of virtual objects while recording” in Tool > Options window.

I think these are the basic and important points for those who want to use Virtual Object feature in QTP and if I’m missing something please update with your valuable comments

QTP Shortcut Keys

My first CTO says that if you want to be smart user of the system, use shortcut keys to handle your system. So I thought that why should not post the list of QTP shortcut keys for QTP users

May be in these most of shortcut keys are common for most of guys but here most of guys are still newbie in QTP.

Ctrl + N- Creates a New Test

Ctrl+Shift+N- Creates a New Business Test

Ctrl+Alt+N- Creates a New Application Area

Shift+Alt+N- Creates a New Function Library

Ctrl+O- Opens an Existing Test

Ctrl+Shift+O- Opens an existing business component

Ctrl+Alt+O- Opens an existing Application Area

Shift+F2- Rename the Action name

Ctrl+M- Make the comment on current row

Ctrl+Shift+M- Remove the comment

Ctrl+Space- Completes the word if you are typing any VBScript method or object in Expert View

F12- For Standard Checkpoint

Ctrl+F12- For Standard Output Values

F7- Step Generator

F8- New Step in Keyword View

Shift+F8- New Step after block of statement

F3- Recording

F4- Stop the Recording

F5- Run the Script

Ctrl+F5- Run the selected step in the script

Ctrl+R- Open the object repository

Shift+Alt+F3- Analog Recording

Ctrl+Shift+F3- Low Level Recording

F11- Step Into

F10- Step Over

Shift+11- Step out

Ctrl+F10- Run to Step

Ctrl+T- Adds the selected item in the Watch tab

Ctrl+F7- Check the Syntax error in the script.

Ctrl+Page Up or Page Down- Toggles between the Keyword and Expert View.

You can add more if I’m missing some shortcut keys.

Quality Center-9.2

There are five major modules which are used to organize and manage the test project.

  • Releases
  • Requirements
  • Test Plan
  • Test Lab
  • Defects

In Quality Center, these are the phases for any test projects.

Releases

For the Releases module, there are two main terms that is-

  • Release
  • Cycle

Release- Release represents a group of changes in the application which will be present in the same application after some duration.

Cycle- A cycle represents a development and QA cycle based on the project time line.

Note- The Release and Cycles have defined start and end date.

Step to define Release and Cycles

Open the QC – Give username and p/w – Select your domain – Select Project – Now login in the QC – Click on Releases button on the sidebar – In the right hand side, select root Releases folder – Click on New Release Folder icon link – New Release folder pop-up comes – Enter Release Folder name ex. ABC – Click OK – Release folder will be added under root Releases folder – Now add sub-folder under ABC – Select created ABC folder – Click New Release icon link – New Release dialog opens – Enter your release name ex. UI – Click OK – Enter Start date, End date and Description for the release – Now the time to add cycle in release folder – Select release folder UI – Click New Cycle icon link – Enter cycle name ex. XYZ – Click OK – Enter Start date, End date, and Description in right side panel.

Requirements

In Requiremnets module we describe that what needs to be tested in the application. There is one important term that is-

Reuirement Tree.

Reuirement Tree- This is a graphical representations of your requirement specification, displaying requirement hierarchically.

Steps to define Project Requirements

 Click on Requirements button on the side bar – Choose View menu – Select Requirement Tree – Create new requirement folder – Select root Requirements folder – Click New Folder icon link – Enter folder name in Create New Requirement Folder ex. Some_Project in dialog box – Click OK button – Requirement folder will be added in requirement tree – Select created folder Some_Project – Click New Requirement icon link – Select Requirement Type (Functional) and in Requirement Name enter “Fucntional Testing” – Click OKNew Requirement dialog box opens – Enter Priority and select your project – Click Submit button – Click Close button – This folder will be added under Some_Project folder – Now add a child requirement – In the requirement tree make sure Functional Testing requirement folder should be selected – Click New Requirement icon link – Select Requirement Type (Functional) and in Requirement Name enter “members” – Click OKNew Requirement dialog box opens – Enter Priority and select your project – Click Submit button – Click Close button – It will be added child requirement under Functional Testing folder – Now assign the requirement to a Cycle – Select your requirement – Choose Requirements Assign to CycleAssign to Cycle dialog opens – In the release tree, expand the tree and check the checkbox for cycle – Click OK button – Click Yes – Now check the Target Release and Target Cycle in details page.

Converting Requirements

In this functionality, we have to convert all requirements folder tree to Test Plan module. We do this because of similar folder tree in both Requirements and Test Plan modules.

When we can stop the Testing?

This is very good question for any QA executive and testing guys that when we can stop the testing?

In software world we can not say that particular software is bug free and there is no bug that is why testing process is going continuous. But we always try to give perfect and reliable system but here is the question that how? So there is no predefined explanation for stop the testing process, just like you can not say that when we want to develop the system. Its totally depend upon our needs and requirements. If we need something specific to complete our requirements then we start thinking about new system or application. Same as going with testing process also but with the help of some factors like Time, Budget, Risks, Bugs and etc, we can decide the exit point. May be all these are not applicable in one time always but one of them is playing important role to stop the testing process.

Budget of the any object is playing very important role to define the existence of it. In software development planning we break the budget in different sections that how much we can spend in particular section? So if we have specified budget for testing then we complete the testing in given time. Time and Budget are also important factors to decide the exit point of testing. If we have reviewed and tested all risk area of the system in a given time then we can stop the testing. To decide the exit point of testing phase we check the bug rate also, if bug rate is too low then and if we don’t have enough time and budget then also we can stop the testing.

According to my thinking these are some basic factors to stop the testing. If I am going in wrong way then come and share your thoughts also.

V and Butterfly Models

One day one of my friend asked me about testing models and I have not given satisfactory answer to him. But that does not mean that I was not aware about testing model, I was, but not that satisfactory points to convince him. So today I am going to write something about testing models. Basically I am going to describe both V and Butterfly models. So for newbie, Testing Model is a conceptual model that defines the steps which are using to test the any application. V model defines in V shape. Left line of V model depicts 4 things-

  • Requirement Analysis
  • System Design
  • Architecture Design
  • Module Design

while joining point of both line depicts Coding. In V model left line processes are coming from Up to Down while in right line processes are going Down to Up. Right line also depicts four things –

  • Unit Testing
  • Integration Testing
  • System Testing
  • Acceptance Testing.

Now we discuss about Butterfly model. Butterfly model is also a testing model that in butterfly shape. Left wing of butterfly depicts Test Analysis and right wing depicts Test design and finally body of the butterfly depicts execution of the test.

Here I am giving only my opinion about these model if you guys feels it is also not satisfactory content about testing model then I will wait for your words.

Interview Questions of Software Testing

What’s the Software Testing?

A set of activities conducted with the intent of finding errors in software.

What’s the Test Plan?

A high level of documents that define the software testing project.

What’s the Test Case?

A set of test inputs, execution, and expected result developed for a particular objective.

What’s the Test Log?

A chronological record of all relevant details about the execution of a test.

What’s the Test Data?

The actual values used in the test or that are necessary to execute the test.

What’s the Database testing?

In database testing, we can check the integrity of database field values.

What’s the Defect?

The difference between the functional specification and actual program text. Read more

Interview Questions of Bugzilla

What is Bugzilla?

Bugzilla is a bug tracking system developed at mozilla.org.

How do enter a bug in Bugzilla?

To enter a bug, through "Enter a new bug" link from the main Bugzilla page. This will take you to a product selection screen.

What happens once enter a bug?

After you enter a bug, mail is sent both to you and the QA department. A member of the QA department will verify that they can reproduce your bug.

How do search a bug?

To search a bug, through "Query" link from the main Bugzilla page.

How do submit a patch?

The new Bugzilla system supports the attachment of patches, test cases, and various other forms of file types directly from the bug report screen. Just click on "Create an attachment"

Are cookies required in Bugzilla?

Yes. Read more