TEST THE RISK!

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

As I tried to explain in my previous posts Selenium is an automation framework for web application and Webdriver is the newer version of Selenium RC. I have used Selenium Webdriver for automatizing web application with version of selenium-2.25.0-py2.7.egg which prepared for the Python. However there are newer version this Webdriver package.In this post I explain how to update Webdriver version on Windows. If you check the site-packages folder where the Webdriver installation folders are present, you can see the related folder. In this folder there is easy_install.py which is used upgrading. If you can't find this file first you need you install setuptool . To update the Selenium version, you can follow the instruction below: Check easy_install file in the directory like as C:\Python27\Lib\site-packages if there is easy_install go to next step, if you don't have it install setuptools from here. Download Selenium newer version from here . Select the link what language

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%.

Test is easy when you know how to test! However, test is hard if you know the just the meaning of 'test'. There are lots of test techniques, mainly static and dynamic tests . However the static test techniques focus on the code with out running it, dynamic test techniques focus on the functions with running the code. Therefore the differences can be explained by the meaning of static and dynamic .  In this post, I want to explain one of my experiences about the importance of static testing. Static testing has the following sub-title as: review, inspection, walk-through, desk-checking, proof-reading. Every item can be done by different people with different method and different level of formality. While the  inspection can be viewed by experienced person in very formal way leading by a moderator, walk-through can be performed by coder in order to give some information about the work. To get more information about static testing, you can read this post in Turkish.  Th