Skip to main content

About m

About Me

Welcome to my corner of the web! I am Mesut Güneş, I'm thrilled to share a bit about myself with you.

Who am I?

I'm a seasoned software developer with a passion for automation, a love for sports, and an insatiable curiosity for all things tech. My journey in the world of software began back in 2007 when I first dipped my toes into coding. Since then, I've been on a fascinating adventure, navigating through various aspects of software development.

My Passions

Tennis & Running

When I'm not immersed in lines of code, you can find me on the tennis court or pounding the pavement on a refreshing run. Sports have always been an integral part of my life, offering a perfect balance to the mental challenges of programming.


Programming isn't just a career for me; it's a creative outlet and a continuous learning experience. I've spent years honing my skills, exploring different languages and paradigms, and tackling exciting projects.

Evolution of Focus

While my journey began as a software developer, my interests evolved over time. In 2010, I stumbled upon the fascinating world of test automation. The idea of streamlining processes and improving efficiency resonated deeply with me. Soon after, I found myself delving into the realm of DevOps, where I discovered the power of automation in accelerating software development.

My Mission

My primary focus is on automating every facet of the development pipeline. From testing to deployment, I'm passionate about leveraging automation to optimize workflows, enhance quality, and expedite delivery. Open-source tools and technologies form the backbone of my approach, fueling innovation and collaboration.

Sharing Knowledge

I firmly believe in the importance of knowledge sharing. Over the years, I've had the privilege of presenting talks on testing at various meetups and conferences. Additionally, I've authored blog posts and created educational materials to empower fellow developers and enthusiasts on their automation journey.

Let's Connect!

Whether you're a fellow enthusiast, a curious learner, or someone looking to collaborate, I'd love to connect with you. Feel free to explore my website, reach out with questions or ideas, and let's embark on this exciting journey together!

Thank you for stopping by!

Mesut Güneş

Anything on this site reflects my thoughts about the subject mainly on software testing so reference documents are not responsible for any misleading pieces of information on the site, that's because of my understanding. I recommend reading reference documents.

Any questions/requests/recommendations are welcome. Also, feel free to share my mistakes in my posts and in my documentation anywhere. You can send me an e-mail by filling out this form.

Please fill in the form below to get in touch with us.

Your Name

Your Email *

Your Message *

Popular posts for software testing and automation

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\", line 10, in <module>     m.login()   File "D:\workspace\ sample_project \", 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

Change Default Timeout and Wait Time of Capybara

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

Create an Alias for Interactive Console Work: Selenium and Capybara

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, :  Creating Aliases Depends on your favourite shell, you need to add the alias to .bashrc bash

Page-Object Pattern for Selenium Test Automation with Python

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

Performance Testing on CI: Locust is running on Jenkins

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