capycon - New Ruby GEM for Running Capybara on Console


Testing is enjoyable if you are using the right tools and technologies, of-course you also need to understand the philosophy behind the testing. I generally use testing tools interactively to try different options that the tool you are using gives as alternatives. For Selenium and Capybara, I have scripts to run get to get them ready on my console, you can read more this post for Windows and this for Unix-like. Under the quarantine days, I wanted to create a Ruby GEM for any want to get Capybara experience on the console for their project. 


Capycon is simple, the short version of Capybara-Console, a GEM file so you can install it by:

gem install capycon

To use it, open your terminal and switch irb or pry and then require the capycon, then you use all the functionality of the Capybara on the console. See the following steps;
~/P/p/c/capy_con (master ⚡→☡) pry
[1] pry(main)> 
[2] pry(main)> require "capycon"

  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
  *                                                                           *
  *                capycon - CAPYBARA CONSOLE                                 *
  *                                                                           *
  *  Default driver is :driver_iphone6_vertical_visible                       *
  *  To set the site name as environment variable:                            *
  *    echo 'export SITE_NAME=http://www.github.com' >> ~/.bash_profile       *
  *                                                                           *
  *  To set the driver  as environment variable:                              *
  *    echo 'export DRIVER=driver_chrome_visible' >> ~/.bash_profile          *
  *                   OR                                                      *
  *  You can set the driver by one of the following options                   *
  *                                                                           *
  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

    Capybara.current_driver = :driver_chrome_visible
    Capybara.current_driver = :driver_chrome_fullscreen_headless
    Capybara.current_driver = :driver_iphone6_vertical_visible
    Capybara.current_driver = :driver_iphone6_vertical_headless
    Capybara.current_driver = :driver_iphone6_horizontal_visible
    Capybara.current_driver = :driver_iphone6_horizontal_headless
    Capybara.current_driver = :driver_iphone6plus_vertical_headless
    Capybara.current_driver = :driver_iphone6plus_horizontal_headless
    Capybara.current_driver = :driver_ipad_vertical_visible
    Capybara.current_driver = :driver_ipad_horizontal_visible
    Capybara.current_driver = :driver_ipad_vertical_headless
    Capybara.current_driver = :driver_ipad_horizontal_headless
    Capybara.current_driver = :driver_samsungs6_vertical_headless
    Capybara.current_driver = :driver_samsungs6_horizontal_headless
    Capybara.current_driver = :driver_samsungsTabA_horizontal_headless
    Capybara.current_driver = :driver_samsungsTabA_vertical_headless
    Capybara.current_driver = :driver_desktop_headless
=> true
[3] pry(main)> Capybara.current_driver = :driver_chrome_visible
=> :driver_chrome_visible
[4] pry(main)> visit "/"
=> nil
[5] pry(main)> find(".js-site-search-form > label > input").send_keys "capycon"
=> #<Capybara::Node::Element tag="input" path="/HTML/BODY[1]/DIV[1]/HEADER[1]/DIV[1]/DIV[2]/DIV[2]/DIV[1]/DIV[1]/DIV[1]/FORM[1]/LABEL[1]/INPUT[1]">
[6] pry(main)> find(".js-site-search-form > label > input").send_keys :return
=> Obsolete #<Capybara::Node::Element>
[7] pry(main)> page.has_content? "gunesmes/capycon"
=> true

When you require the capycon, it automatically opens www.testrisk.com with Chrome driver by default. But you change the current driver by one of the following in the list. If you always want to open the URL as SITE_NAME that you generally test with the driver you want, you set them as environment variables in your bash_profile. For this run the following commands:

echo 'export SITE_NAME=http://www.github.com' >> ~/.bash_profile
echo 'export DRIVER=driver_chrome_visible' >> ~/.bash_profile

I will be appreciated to get feedback from you on GitHub.

Popular posts from this blog

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

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\selenium\webdriver\r
Read more

Change Default Timeout and Wait Time of Capybara

Image
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

Getting the text of elements in Espresso

Image
Espresso is not designed to play with UI objects. When you are considering it in terms of capability for testing, it needs to be improved more. It is not as mature as Android SDK itself so you need to customize somethings to handle your requirements. Even you may need to use other tools like UIAutomator integrated into your test suite. In this post, I want to show how we can handle getting the text of ViewInteraction view.  ViewInteraction view does not have .text function for getting the text of the object since it is designed to interact with the object. Another method which may solve the problem of the assertion is to use the .check for matching the text, as follows: However, this method is not a good way to assert that a certain field text equals a value. For this purpose, we need to get the text of the element and assert it. To get the text of the ViewInteraction element, we need to cast it to TextView with getting the assignable form of it then
Read more

Performance Testing on CI: Locust is running on Jenkins

Image
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 should be so
Read more

How to Set Shared Preferences in Espresso Test for Kotlin and Java

Image
I have experienced Espresso and needed to deep dive into Shared Preferences just because it is one of the main parameters used in the application we developed. As a long search in the online sources but there are some pretty old documents for Espresso with Java and very few documents about Espresso with Kotlin. In this post, I want to share my experiences with setting Shared Preferences with Kotlin and Java and how you can use it in your test design. You can follow up the steps for your test project. Shared Preferences is a way to store user data in local devices so it has been supported since the very early version of Android. Shared Preferences can be stored in the default file or custom file.  Using Default File for Shared Preferences If your application uses the default file it should stores the shared data in the default file provide by Android as in the following path in the device: /data/data/com.package.name/shared_prefs/com.package.name_preferences.xml This
Read more