Do Testers and Programmers have Conflicting of Interests?

Testers test the applications which are developed by developers belonging the output of the analysts. Analysis - Development - Test is trivet for software development projects and absence of one or not ideally running one of these steps can lead software project to fail. However, in high level thinking we may characterize analysts as solver, developers as producer, and testers as destructor because the major tasks of each role need these kinds of abilities. As a consequence, developers and testers have different abilities and different tasks, which may be concluded that they have opposite tasks such as one is to develop and one is to destruct the software; so they may have seen as having conflict of interest. In this post, I want to explain why the testers needs to search a way to destruct the software product which developers have already made an effort on it.

The testing stage, for me not a stage it is a groups of activities from beginning to the end of software development life cycle (SDLC), covers if system under test (SUT) is developed as what user wanted and, if the SUT reaches the standards. By testing, we may sometimes need to search how the application behave un-expected way. To accomplish this task, we need to think beyond the analyts, because we learn the application during test and can make an assumption about the point which is error-prone. Actually this is the base of exploratory testing, but it is more than this and it requires a well-trained testing knowledge and experience.

There some important key factors affects the degree of the quality perceived by the people who work together to produce a software product. This can be listed as test strategy, test approach, risk, maturity of production environment and test environment, experience of the people, system reqıirement, number of user, profile of the users, domain, and ect. The most important one may be test strategy. Test strategy is a defined rules which everyone has knowledge about how to test the SUT and if any defect found, everyone can be estimate how the defect can be classified and know the procedure for resolution of the defect, more about test strategy read this. Therefore, test strategy is a common knowledge for the organisation and can be applied if any controversy has been occurred. This is important because it can be pro-active approach for this case: sometimes testers may test more than what the organisation want and requires more time than expected or developers may submit less quality product for testing than expected also re-work cycle can be longer than expected.

To sum up, testers should find a way to destruct the SUT so that it can be reach to aimed quality level and the developers should also know this and it helps to tester for finding defect by explaining the structure of the codes. This requires wisdom. Sure this is a feature of a good development environment, but the un-smart development organisation may not have this. To remember what a smart which is defined by Ivar Jacobson:

Unsmart with Testing – having two classes of people – developers and testers. Unsmart projects testers are “the cleaners in the software world” – picking up the mess left by the developer.

Smart with Testing – the whole team is jointly responsible for quality and testers are first-class citizens

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