What are different Recording Modes in QTP?

There are three basic Recording modes in QTP:

1) Normal recording in QTP:

It is used for recording the operations perform at different contacts on the standard GUI objects. During this all actions are recorded with Objects details in Object repository. It will generate the corresponding test script statement for every user action. It will also store the required related information in the object repository.

QTP records in Normal mode by default and takes full advantage of QTP Object Model , recognizing application objects regardless of their location on screen.

2) Analog Recording in QTP

           It is used for recording the continuous operations. This is useful for the cases where we need to record exact mouse or Keyboard operation in relation to Screen or application. This is useful when Normal reocrding does ot work for you. E.g.- It will be helpful where we want to record mouse drag operation.

3) Low-level Recording in QTP

           It is special recording mode provided by QTP, which is used for recording the minimum operations   on  the Non-Supported environments also.





This mode records at object level and records all run-time objects as windows or winobject test objects. You can also use this recording mode in case exact coordinates are important for your testing.

What is the basic difference between Structural and Functional Testing?

Different people use different Software terminologies as per their convenience  and here are two more which are used in Software Industry, specifically among Quality Prfessionals.

Structural testing is about comparing software behavior against the apparent intention of the source code wirtten to execute it. Many testers call it White-Box Testing or Glass-Box Testing :) Structural testing is also called path testing since you choose test cases that cause paths to be taken through the structure of the program.


Other the other side, functional testing is about comparing workflows behavior in the application against user requirements specification. This is also called as Black-Box Testing.

Structural testing verifies how the program works by considering possible pitfalls in the structure and logic. In Functional testing, nobody is bothered about the internals. It simply focuses on the end results and way they are delivered to users.

What is Code Coverage and how does it impact Software Quality?

I would like to take second question first: Code coverage is considered as an extended step towards ensuring good quality of the software by indirect means. Why I explained it in this way?

In my opinion Code coverage is more about assuring quality of test-cases and finding redundant code, not about quality of actual product we are developing. Realistically its very difficult to do Code coverage exceises with actual testing. So normally teams Quality Engineers try to find out the cases they need to add and test-cases which does not help in improving the coverage.

You may not agree, as its my personal opinion.

Now lets come to first question about what it is?

Code Coverage is methodology to:

1.  Find different program areas not excercised by Testers through pre-identified set of Test cases.
2. Add new test cases to increase coverage in terms of Functional/Statement/Decision/Conditional-coverages
3.  Identify overall gap between the actual coverage and targetted coverage. Its more about statistics which helps a Quality engineering team to know about the other quality measures of a Software.
4. To identify redundant test-cases which have 0% contribution in coverage increase.

Most of the times last point is not considered but we should not forget that its also a wastage of resources/time when we run redundant test-cases which adds no value.