How to set the ‘Replay Type’ in QTP?

The first line in the below code will give the control to Mouse and the last line will give the control back to QTP for better Mouse operations.

E.g.,

Setting.WebPackage("ReplayType") = 2

Browser(“Browsername”).Page(“Title”).Webedit(“Search”).FirEvent “onmouseover”

Setting.WebPackage("ReplayType") = 1

Comments

Post a Comment

Popular posts from this blog

Waterfall Model in STLC

Image
What is Waterfall Model?                     The  waterfall model  is a sequential design process, used in software development processes, in which progress is seen as flowing steadily downwards (like a  waterfall ) through the phases of Conception, Initiation, Analysis, Design, Construction, Testing, Production/Implementation and Maintenance.                                                         Waterfall Model   The Waterfall Model was first Process Model to be introduced and so it is called as the  traditional approach to software development .It is also referred to as a  linear-sequential life cycle model .  It is very simple to understand and use.  In a waterfall model, each phase must be completed...
Read more

Latest Version of TestComplete

 TestCompletes latest version as of February 2023 is -  15.48.6 (Jan 31, 2023) TestComplete supports various testing types and methodologies, for example: Functional and GUI testing Unit testing Regression testing TestComplete has 3 window layouts: Design-time - used when you view and edit tests, Recording - used when you record tests, Playback - used when you run and debug tests.
Read more

Successful tester

  Software Tester must  possess the below guidelines  t o be successful, • Concise:  As simple as possible and no simpler. • Self-Checking:  Test reports its own results; needs no human interpretation. • Repeatable:  Test can be run many times in a row without human intervention. • Robust and logical:  Test produces same result now and forever. Tests are not affected by changes in the external environment.  • Sufficient:  Tests verify all the requirements of the software being tested. • Necessary:  Everything in each test contributes to the specification of desired behavior. • Clear:  Every statement is easy to understand. • Efficient:  Tests run in a reasonable amount of time. • Specific:  Each test failure points to a specific piece of broken functionality; unit test failures provide "defect triangulation". • Independent:  Each test can be run by itself or in a suite with an arbitrary set of other tests in any order...
Read more