Service Virtualization

 View Only
  • 1.  Why is my web recorder not recording the steps?

    Posted May 23, 2016 02:38 PM

    I launch web recorder and perform the steps for my test case.  When i click stop recording no steps are logged.  This occurs with the internal browser as well as an external browser.



  • 2.  Re: Why is my web recorder not recording the steps?
    Best Answer

    Broadcom Employee
    Posted May 23, 2016 03:19 PM

    The HTTP proxy recorder in Application Test will only record what is going over the wire between a web browser and a server.

    If there is any rich UI frameworks involved in the web application, you will not be able to record and play back since the HTTP Proxy Recorder is not a browser simulator.

    If you are looking doing a browser simulation recording (as in driving a UI) you need to use Selenium to accomplish the recording.

     

    Below is some documentation on using Selenium:

    There has been a change to Selenium Builder since this documentation, Selenium Builder 3.0.9 is what now comes with Firefox.

    You cannot run locally anymore from Selenium Builder, you need to run from Selenium Server. This is just a jar file that gets downloaded and then when you execute the jar file it runs like this example: (Current Selenium Standalone Server is 2.53.0)

     

    C:\SeleniumServer>java -jar selenium-server-standalone-2.50.1.jar

    10:34:56.286 INFO - Launching a standalone Selenium Server

    10:34:56.537 INFO - Java: Oracle Corporation 25.71-b15

    10:34:56.538 INFO - OS: Windows 7 6.1 amd64

    10:34:56.572 INFO - v2.50.1, with Core v2.50.1. Built from revision d7fc91b

    10:34:56.733 INFO - Driver class not found: com.opera.core.systems.OperaDriver

    10:34:56.734 INFO - Driver provider com.opera.core.systems.OperaDriver is not registered

    10:34:56.741 INFO - Driver provider org.openqa.selenium.safari.SafariDriver registration is skipped:

    registration capabilities Capabilities [{browserName=safari, version=, platform=MAC}] does not match the current platform VISTA

    10:34:57.162 INFO - RemoteWebDriver instances should connect to: http://127.0.0.1:4444/wd/hub

    10:34:57.163 INFO - Selenium Server is up and running

     

     

    Once you record your website, when you play it back in Selenium Builder the information you need will be in the display like above.

    Selenium Server can be gotten from: http://www.seleniumhq.org/download/

    Devtest Selenium links:

    "https://docops.ca.com/devtest-solutions/9-1/en/reference/test-step-descriptions/selenium-integration-steps/create-and-export-a-selenium-builder-recording"

    "https://docops.ca.com/devtest-solutions/9-1/en/reference/test-step-descriptions/selenium-integration-steps/import-a-selenium-builder-json-into-ca-application-test"

    "https://docops.ca.com/devtest-solutions/9-1/en/using/using-ca-application-test/using-the-workstation-and-console-with-ca-application-test/running-test-cases-and-suites/run-a-selenium-integration-test-case"

     

    Hope this helps.



  • 3.  Re: Why is my web recorder not recording the steps?

    Posted May 23, 2016 03:49 PM

    I was unable to use selenium builder.  I create a test case and everything is good when recording, but when playback occurs, 2 things are wrong.  One being file upload and 2 a change in URLS.  I spoke with Shiney about this, and was told is a Selenium Builder issue not CA.  And from all the documentation I can find on Selenium Builder, there is nothing about file upload.



  • 4.  Re: Why is my web recorder not recording the steps?

    Broadcom Employee
    Posted May 23, 2016 04:34 PM

    If you are unable to playback in Selenium Builder, it will not playback in DevTest.

     

    I would do a search for on how to Upload File with Selenium.  Once you are able to get it working with Selenium Builder playback, try it in DevTest.



  • 5.  Re: Why is my web recorder not recording the steps?

    Posted Jan 17, 2017 03:55 PM

    Samuel,

    Were you able to get it working in Selenium Builder as Marcy recommended? If so, were you able to get it to work in DevTest?