Eggplant GUI (graphic user interface) ve mobil uygulamaların testlerinde kullanılabilecek oldukça yararlı bir test otomasyon aracı olarak görülebilir. Ayrıca perfomans testlerinde de kullanılabilme imkanı sunuyor. Kendine has bir dil ğeliştirilmiş ve bu sayede hızlı bir şekilde test scriptleri yazmak mümkün. Test suite üzerinde hiç bir yazılım bilgisi olmaksızın komutları ekleyerek istenilen script kolaylıkla hazırlanabilir. Burada değinilmesi gereken bir başka yenilik ise Image Doctor olarak adlandırılan bir özelliği ile resmi alınan buton veya herhangi bir objenin ekran üzerinde aratılarak buldugunda uygun fonsiyonu yerine getirmesi istenilebilir. Yani test edilen uygulamanın teknolojisi göz ardı edilebilir. Kaydedilen imajları tekrar tekrar farklı test case hazırlanırken kullanılabilir. Bu sayede hız kazanabilirsiniz.
Eggplant vs Platform
SUT (system under test) test edilecek sistem olarak geçen sistem demektir. Mobil cihazların testleri için genel mantık ise test edilmek istenen uygulamanın çalışacağı mobil cihaza (SUT) VNC Server kurularak Eggplant'ın kurulmuş olduğu bilgisayar bağlanmak gerekir. Bu bilgisayar yardımıyla test scriplerini üreterek VNC yardımıyla SUT'a bu komutları gönderebilir. Bu sayede bir simülatör/emülatör yardımıyla değil gerçek bir mobil cihaz üzerinde otomasyon kodlarını çalıştırma imkanı sunuyor. Bu açıdan VNC ile bağlantı kurabileceğiniz her hangi bir cihazda mobil uygulamalar test edebilirsiniz. Yani platform bağımsızdır.
Eggplant Değerlendirme
Artıları:
Gerçek cihazlar üzerinde test imkanı
Platform bağımsız
Kısa öğrenme süresi
Image Doctor, kaydedilen imajlar ile kolay ve hızlı test case hazırlama
Farklı işletim sistemlerine kurulum (Windows, Linux, Mac)
Eksiler:
VNC Server gibi ek bir uygulama gerekliliği ve maliyeti
VNC serverde kopmalar olabilir
Ücretli bir uygulama. Daha gelişmiş Hp QTP ve IBM Robot'a kıyasla çok daha ucuz
Küçük bir kullanıcı kitlesi. Kötü bir destek sayfası.
Test ettiğim Eggplant v12.10 sürümünde rahatsız edici kırpılmalar söz konusu. Bu durumun geçici olduğunu düşünüyorum.
Test ettiğim sürüme ait görselleri altta bulabilirsiniz. Turkcell T20 android sistemli telefonuma kurduğum iki farklı ücretsiz VNC server (droid VNC ve VNC Server) uygulaması kullanarak iki farklı test case hazırlayabildim. Eggplant Test Suite görselinde kullanılan dilin sadeliğini görebilirsiniz.
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
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
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 alias to .bashrc bash
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 asserting your test cases against to the
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
