Working Mechanism of QTP

Hello everyone, welcome back to all to my blog….

Last time we discussed about what is automated testing and a brief description about QTP. I had also pointed out some basic working mechanisms of QTP. Actually it is just a theoretical knowledge but quiet useful if you are a new to QTP and want to learn it. By following the basic methods you can easily test the application on you own.

I hope this blog can help you guyz a lot in gaining more knowledge in QTP.

The basic working mechanism of QTP are as follows:

a)    Recording

b)    Object Identification

c)    Expert View

d)    Parameterization

e)    Checkpoints

f)    Output Values

g)    Report.Report Event

a)    Recording

1. Simply records the activities that is performed by the tester.
2. QTP remembers and uses the same settings for additional record sessions on the same test.

b)    Object Identification

1. Uses “Human” like technology.
2. Learn properties of a GUI object at record time.
3. Compares the stored object properties with actual properties.
4. Stored object and its properties is called Test Object.
5. Quick Test is also known as “Test Object Model”.
6. Concept of Object repository.

c)    Expert View

1. Each line represent a Test Step in VB Script.
2. Object’s Name is displayed in parentheses following the Object Type.
3. Objects in Object Hierarchy are separated by a “dot”.
4. Operation performed on the object is always displayed at the end of the statement.
5. Syntax for a statement in Expert View

d)    Parameterization

1. Executing test using the dataset.
2. Parameterization allows us to pick different values at run time.
3. It Reduces Time and Effort.

e)    Checkpoints

1. Verification point that compares the current value with the expected value for specified properties of an Object.
2. Generates a PASS status otherwise FAIL status.
3. Types of Checkpoints.

• Page Checkpoint
• Bitmap Checkpoint
• Image Checkpoint
• Text Checkpoint
• Accessibility Checkpoint
• Database Checkpoint
• Table Checkpoint

f)  Output Values  

1. It is a step in which a object property value is  captured at a specific point.
2. Values are stored at a desired location.

g)    Report.Report Event

1. To report custom test steps in QTP’s test results.
2. Syntax –
3. Event Status can have values

•  0 or micPass  sends a pass status to test result window
•   1 or micFail sends a pass status to test result window
•   2 or micDone sends a message to test result window without affecting the Pass/Fail status
•   3 or micWarning sends a warning message to the result window

This much for today, hope this will give you all some idea about QTP. These are some methods or working mechanisms that I pointed out which are very essential while testing using automated testing tool i.e. QTP.

I will try to more information about Script generation in the next post till then find more bugs 🙂

Quick Test Professional

Hello everyone…

Today I am going to share some of my knowledge in QTP with you all. Actually I am also new to this tool and just started my career after being graduated as an Engineer.

In my perspective, when we come across functional testing, then QTP is the first automated tool that comes in our mind if we are talking about functional testing. But to understand the main concept of QTP, we should be able to understand what is automated testing and its advantages and disadvantages…

AUTOMATED TESTING

• Use of software to control the execution of test.
• Comparison of actual and predicted outcomes.
• Test reporting.
• Organized for Short Term Goal Achievement
• Testing progress when supported by dedicated programmers who are directed by testers.

Now, brief information about QTP (Quick Test Professional)

• Flagship functional testing tool from Mercury Interactive.
• Also known as HP Functional Test.
• Icon based tool which automates the functional and regression testing.
• Boon for both technical and non-technical testers.
• Easy to use, understand and program.
• Use VB Script.

                                                                    

Basic Working Mechanism of QTP

• Recording
• Object Identification
• Expert View
• Parameterization
• Checkpoints
• Output values
• Reporter.Report Event

 

The detail information about the working mechanism will be posted in my next post…. till then keep smiling and happy testing…

Manual Testing Vs Automated Testing

Automated testing is very crucial in any Software development organization in order to run the software testing activities smoothly. But it is not always compulsory to have automated testing going all the whole time. Manual testing is also equally important.

Here, are the some tips that you would like to have if you are interested in functional testing and like to use tool Quick Test Professional by HP.

Before starting any automated testing tool lets us figure it out which one is better Automated testing or Manual testing…

1. In term of Judgmental: If we are testing a software in which several decision are to be made then in those case Manual testing will be far more better then Automated testing.
2. Specific repeatable results every time: If we are getting the same types of result every time then, in those case it is suitable to go through Automated testing. But if we are having dynamic condition then go for Manual testing.
3. Results: If we are testing the results of a particular function, then go with Automated testing if the result are  in the form of strings or numbers. But if the result are in the form in images then you have to use Manual testing.
4. Repetitive: Machine never get bored of testing the same things again and again. But human beings can get bored and at the meantime they can miss several issue. So use Automated testing if repetitive testing are required.
5. Regression testing: When a particular bug is fixed, then while fixing it, others part of the software get can effected as a side effect. So, it is much better to used Automated testing to find out the new issues after bugs get fixed.
6. Testing with limits or boundaries: Well i guess computer are good in counting and rarely make mistakes (except GIGO condition). So, I would prefer going with Automated testing rather then Manual testing. Since, human beings requires to visually check the characters and that may lead to errors in most of the cases.
7. Test include characters that are hard to distinguish: Automated testing can easily figure out the difference between the ‘o’ (small o) and ‘0’ number zero.
8. Pop-up error messages handling: It is much better to use Manual testing while testing the pop-up messages rather can using Automated testing. Since, human being can understand the message.

Remember this steps while testing. Catch you all in next time..

Till then… happy testing and keep finding more BUGS….