Skip to main content

Quick starting to Selenium

Image
By
Selenium IDE

Selenium IDE is an open source test automation tool, actually a plug-in for firefox. Basically, it enables user to record a test case and replay it on firefox. However with the other features of selenium, more sophisticated works can be done by selenium.

Following instructions can be followed for the installation and the use of Selenium IDE:
         1. Install the latest version of Selenium IDE
              > http://release.seleniumhq.org/selenium-ide/

         2.  Open Selenium IDE
              > Firefox > Tools >Selenium IDE

        


Selenium Remote Controller

With the remote controller, written test scripts can be run on the different browsers. Test script can also be written in  C#, Java, PHP, Python ot Ruby so complex test cases can be written by desired programming language. Remote controller is a server prepared by Java so every time virtual apache server runs on the computer with the default port 4444.

Following instructors can be followed for the installation and the use of Selenium RC:
         1. Install the latest version of Selenium IDE
             > http://release.seleniumhq.org/selenium-ide/

         2.  download the latest version of selenium server
             >  http://www.nuget.org/packages/Selenium.RC

         3.  Check the Java version
             > java -version
                    

          If it gives an error, update the Java JRE with the latest version
           > http://www.oracle.com/technetwork/java/javase/downloads/jre-7u1-download-513652.html

         4. Test your selenium server by the following command where the selenium server is located at step 3
            > java -jar selenium-server-standalone-2.13.0.jar
           

         You can stop the server by the following commads:
            > CTR + C
            >  wmic path win32_process Where "CommandLine Like '%selenium-server.jar%'"  Call Terminate

         5. After all, you need a test suite to run by the following commands:
           > java -jar <..\..\selenium_server.jar> -htmlSuite *browser <target website> <absolute\path\to\htmlsuite.html> <absolute\path\to\result.html>

           > java -jar d:\selenium\selenium-server-standalone-2.13.0.jar -htmlSuite *firefox http://www.google.com d:\selenium\login.py d:\selenium\result.py


Supported browsers include followings:
  •   *firefox
  •   *mock
  •   *firefoxproxy
  •   *pifirefox
  •   *chrome
  •   *iexploreproxy
  •   *iexplore
  •   *firefox3
  •   *safariproxy
  •   *googlechrome
  •   *konqueror
  •   *firefox2
  •   *safari
  •   *piiexplore
  •   *firefoxchrome
  •   *opera
  •   *iehta
  •   *custom

You can also run selenium server on a different port by adding the port option after the server name like as: java -jar <..\..\selenium_server.jar> -port 5555 ....





  




       



Labels:Software testing

Popular posts for software testing and automation

Selenium Error "Element is not currently interactable and may not be manipulated"

By
Selenium webdriver can drive different browsers like as Firefox, Chrome or Internet Explorer. These browsers actually cover the majority of internet users, so testing these browsers possibly covers the 90% of the internet users. However, there is no guaranty that the same automation scripts can work without a failure on these three browsers. For this reason, automation code should be error-prone for the browsers you want to cover. The following error is caught when the test script run for Chrome and Internet Explorer, but surprisingly there is no error for the Firefox. Selenium gives an error like below: Traceback (most recent call last):   File "D:\workspace\sample_project\sample_run.py", line 10, in <module>     m.login()   File "D:\workspace\ sample_project \test_case_imps.py", line 335, in login     driver.find_element_by_id("id_username").clear()   File "C:\Python27\lib\site-packages\selenium-2.35.0-py2.7.egg\seleni...
Read more

Change Default Timeout and Wait Time of Capybara

By
One of the biggest challenge for automation is handling timeout problem. Most of the time, timeout is 60 seconds but it may sometimes not enough if you have badly designed asynchronous calls or the third party ajax calls. This makes handling timeout more complex. set large enough to tolerate network related problems. For Selenium based automation frameworks, like Capybara, default Webdriver timeout is set to Net::ReadTimeout (Net::ReadTimeout) Changing ReadTimeout If you have timeout problem for Capybara, it gives an error like above. This means that the page is not fully loaded in given timeout period. Even you can see that page is loaded correctly but webdriver wait until the Ajax calls finish. class BufferedIO #:nodoc: internal use only def initialize (io) @io = io @read_timeout = 60 @continue_timeout = nil @debug_output = nil @rbuf = '' end . . . . . def rbuf_fill beg...
Read more

Create an Alias for Interactive Console Work: Selenium and Capybara

By
If you are working on shell most of the time Aliases are very helpfull and time saving. For testing purposes you can use Alias for getting ready your test suites. In this post, I want to explain both running Selenium and Capybara on console and creating aliases for each.  This post is for Windows machines, if you are using Unix-like see   this post . Creating Scripts for Selenium and Capybara First of all, it is assumed that you have installed Selenium and Capybara correctly and they work on your machines. If you haven't installed, you can see my previous posts. I am using the Selenium with Python and the Capybara with Ruby. You can use several different language for Selenium but Capybara works only with Ruby.  Create scripts in a directory called scripts (in your home folder, like as  ~/scripts ) for your automation tool as following, save them as capybara.rb, sel.py :  Creating Aliases Depends on your favourite shell, you need to add the al...
Read more

Page-Object Pattern for Selenium Test Automation with Python

By
Page-object model is a pattern that you can apply it to develop efficient automation framework. With the page-model, it is possible to minimize maintenance cost. Basically page-object means that your every page is inherited from a base class which includes basic functionalities for every page. If you have some new functionalities that every page should have, you can simple add it to the base class. Base class is like the following: In this part we are creating pages which are inherited from base page. Every page has its own functionalities written as python functions. Some functions return to a new page, it means that these functions leave the current page and produce a new page. You should write as much as functions you need in the assertion part because this is the only part you can use the webdriver functions to interact with web pages . This part can be evaluate as providing data to assertion part.   The last part is related to...
Read more

Performance Testing on CI: Locust is running on Jenkins

By
For a successful Continuous Integration pipeline, there should be jobs for testing the performance of the application. It is necessary if the application is still performing well. Generally performance testing is thought as kinds of activities performed one step before going to live. In general approach it is true but don't forget to test your application's performance as soon as there is an testable software, such as an api end point, functions, and etc. For CI it is a good approach to testing performance after functional testing and just before the deployment of next stage. In this post, I want to share some info about Jenkins and Locust. In my previous post you can find some information about Locust and Jenkins. Jenkins operates the CI environment and Locust is a tool for performance testing. To run the Locust on Jenkins you need command line arguments which control the number of clients ,   hatch rate,  running locust without web interface and there s...
Read more