• RSS
  • Facebook
  • Twitter

One Center for all the Testing Need. OneTestingCenter is for all, for all QA, for all Automation. Automation is easy, fun and enriching experience. Happy Learning and Happy Testing!

  • Access to All QA

    At OneTestingCenter, you find lots of books,articles,blogs and detailed guides. Everyone has access to QA. Happy Learning, Happy Testing.

  • Global Trainings

    All the QA/Auotmation trainings are available at OneTestingCenter. QA, Automation, QTP/UFT, Selenium, LoadRunner, QC/ALM, Appium...

  • Automation Learning Fun

    Technology is always evolving. Automation is always challenging. To be frank, Automation is fun, enthusiastic and enrching experience.

    Recovery Scenario Manager

    o   Unexpected events, errors, and application crashes during a run session can disrupt your run session and distort results.
    o   This is a problem particularly when running tests or components unattended—the test or component is suspended until you perform the operation needed to recover.

    So…..Here comes the mechanism to deal such scenarios called Recovery Scenario manager

    ·         Recovery Scenario Manager is a mechanism that helps to deal the unexpected events, errors, and application crashes during a run session
    ·          
    ·         The Recovery Scenario Manager dialog box enables to create recovery scenarios and save them in recovery files.
    ·         We can create recovery scenarios using the Recovery Scenario Wizard, which leads through the process of defining each of the stages of the recovery scenario.
    ·         We then save the recovery scenarios in a recovery file, and associate them with specific tests or components.


    o   A Recovery Scenario consists of the following:
              Trigger Event
              Recovery Operation(s)
              Post Recovery Test Run option

    Understanding the Recovery Scenario Wizard
              Defining the trigger event that interrupts the run session
              Specifying the recovery operation(s) required to continue
              Choosing a post-recovery test run operation
              Specifying a name and description for the recovery scenario
              Specifying whether to associate the recovery scenario to the current test and/or to all new tests





    Recovery Operations Screen

              Keyboard or mouse operations
              Close Application Process
              Function Call
              Restart Microsoft windows
     




    Post Recovery Test Run Options Screen
              Repeat current step and continue
              Proceed to nest step
              Proceed to next action iteration
              Proceed to next test Iteration
              Restart current test run
              Stop the test run













    Reactions:

    QTP - Recovery Scenarion Manager

    Recovery Scenario Manager

    o   Unexpected events, errors, and application crashes during a run session can disrupt your run session and distort results.
    o   This is a problem particularly when running tests or components unattended—the test or component is suspended until you perform the operation needed to recover.

    So…..Here comes the mechanism to deal such scenarios called Recovery Scenario manager

    ·         Recovery Scenario Manager is a mechanism that helps to deal the unexpected events, errors, and application crashes during a run session
    ·          
    ·         The Recovery Scenario Manager dialog box enables to create recovery scenarios and save them in recovery files.
    ·         We can create recovery scenarios using the Recovery Scenario Wizard, which leads through the process of defining each of the stages of the recovery scenario.
    ·         We then save the recovery scenarios in a recovery file, and associate them with specific tests or components.


    o   A Recovery Scenario consists of the following:
              Trigger Event
              Recovery Operation(s)
              Post Recovery Test Run option

    Understanding the Recovery Scenario Wizard
              Defining the trigger event that interrupts the run session
              Specifying the recovery operation(s) required to continue
              Choosing a post-recovery test run operation
              Specifying a name and description for the recovery scenario
              Specifying whether to associate the recovery scenario to the current test and/or to all new tests





    Recovery Operations Screen

              Keyboard or mouse operations
              Close Application Process
              Function Call
              Restart Microsoft windows
     




    Post Recovery Test Run Options Screen
              Repeat current step and continue
              Proceed to nest step
              Proceed to next action iteration
              Proceed to next test Iteration
              Restart current test run
              Stop the test run