Skip to main content

What Reminds from Continous Devilery and Design Conference by Thoughtworks

The conference was hold on September 11, 2014 in İstanbul, Turkey. I want to briefly explain the importance of the conference and what was learnt from it. Thoughtworks, as a well-known consultancy firm in the world, has entered the Turkey's software market. This means that there will be something changes in software industry since there are lots of consultancy firm in Turkey and they have got one more competitor. However this is not an ordinary competitor, they may possibly bring lots of experiences and different kind of consulting culture from the other consultancy firms. 

What is the situation in Turkey?

As I mention, there are lots of software / test consultancy firm but majority of them work as providing developers / tester to companies to work as outsourced. Therefore the guys generally fell alone when doing their jobs because there is generally no technical supports for them to improve their abilities. Also the major problem in Turkey is software development process. Even they don't have a scientific process of development or they have applied some methods without knowing them correctly. Everyone talks about "agile", "scrum", "tdd", "bdd" and some other popular words but none of them know these processes correctly. Their experience generally are based on a book or learnt from an earlier companies incorrectly. Under this conditions, providing some guys to the companies and not giving technical supports to them is useless. It doesn't mean to be a consultancy firm, it is just providing people to some companies' inconsistent process. With this way, there is only one beneficial part to the company that they can request another guy to work with if they don't like him and also these guys don't have companies standart benefits. As  a result, I have met a small amount of people who would like to work for consultancy firms.

What I learn from this conference?

  1. Deployment pipeline: It is the main part of Continuos Delivery. It divides the build system into different functional parts which is to fasten the feed back system and finally brings faster development process. With this way there is an opportunity to parallelize  any stages which makes bottle-necks on the deployment pipeline.
  2. Continues Delivery: Simply, ability to deploy to production. This means that there is always a code that can be deployable to the production. So new features are implemented and tested, another meaning of the feature, it is "DONE", everything works fine. Therefore, we may talk about "one-click-deployment" which means that the features which are DONE can be deployed to the production.
  3. Continuos Deployment: Simply, doing deploy to production. This is one step ahead of continuos delivery. We have  deliverable features on the test servers and then they are deploying to live servers automatically. To enable this feature Fowler mentions that there are two live environment and these are called blue-green environments. Assuming that the blue environment is live, final tests are run on the green environment and if the test are completed successfully by switching router to green-environment and make it live and finally the blue environment is now ready for another deployment.
  4. Automate Everything: Automation is generally understood as automating some test cases but in continuos integration, everything on process can be automated. Building, deploying and test should be automated. To make it possible, we should have configuration management. Another meaning someone should manage these things and write some automation scripts. A new role is needed, this role is different from a classical role system administrators or developers or testers. These kind of operation are handled by DevOps, which means development and operations.
  5. Why Continuos Integration is important: Risk! What ever process we have, we will always have lots of risks. To reduce the risk, we should reduce the delta. For example, deploying 1 week difference to live has low risk than deploying 1 a month difference to live. The level-of-concern (LOC) will depends on the level of difference.
  6. "Done" has different meaning: When the developer say "I finished, it is DONE", it doesn't mean to deploy to live. We still have some test and QA procedure and then if everything is fine and if we deploy the feature to live then we can it is DONE. Done has one meaning is that the feature is live and user can use it. 
  7. Test Strategy: They re-defined the importance of QA procedures. In your organisation, don't ignore the importance of QA engineer. Let them participate, let them test everything, use new approaches like Specification by Example, Generation Testing, Parametric Testing. And sure, automation is must.
  8. Test It Before Get It: Write test cases before the story is implemented so that the minimize the manual effort. We can use cucumber that customer or any business people understand the result so it can increase customer engagement.
  9. These are just related to continuos integration, but there are some other presentation about Design, NoSQL and Consistency and Case Study by
Detail about the conference click here.

Some Pictures from the Conference:     

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