Demands on Testing is Increased

Testing is a key element for software development life cycle (SDLC), the success of testing process can rescue projects from project risks. This awareness leads firms to increase their testing activities by means of having more qualified people and better testing process. Actually the firms are spending more budget for testing activity because of the competitions.

The recent search which is made by Capgemini, Sogeti and HP, about the software testing resource of the firms, shows that comparing the 2012, in 2013 demands on testing is increased. As the beginning of this research, they are saying "As customers demand high performance, error-free application, organization are increasing their budgets and more testing functions are centralized." Let's look at the picture.

Since last year 18% of budget is spent on testing, this year it is increased to 23% of budget. Since last year 41% of the budget is spent on transformational project, this year it is increased to 46%. These show that this year testing has more budget.
Since last year 51% percent of the application are produced as in-house project, this year 41% percent of the application are developed as in-house project. Since last year 8% of organizations have centralized testing function, this year it is increased to 26% of the organization. There is a significant increase on the percentage of having test-center-of-excellence (TCOE), which is 6% to 19%. This is excellence! These infos show that testing organization are becoming more professional.
By increasing the number of mobile application, needs for mobile testing increase. The number on issue for mobile testing is performance with 59%, and the second one is security by 56% which is 18% for the last year. These show that mobile testing is becoming more important issue.

However these are very important steps in software testing, there are still more steps to take the testing one level forward. The main problem is "test environment". Never forget that the success of the testing is as far as the success of the test environment.

These search show that 13% of the projects are tested by production data, 55% of test environment has lack of management, 16% of project were tested by the data created on ad-hoc since the last year it is 5%.
Another setback for the testing success is having starting testing near to deadline which means that there is not enough time for testing, and testing is thought to be performed just in the end. In this search 45% of the organization start testing after development finished.

To reach this study please click the this link.
To reach summary (infografik) of the search click this link.

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

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, sel.py : 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

TEST THE RISK!

Search This Blog