Skip to main content

Posts

Basics of Continuous Integration (CI)

Almost every methodological approach in software development aims to reduce development time and produce more qualified products. Continuous Integration (CI) also aims to reduce development time. Basically, CI is software development practice that developers need to check-out their codes in their local development environment and than integrate them to shared repository. According to Martin Fowler who known by his studies about CI, there should be at least one integration to shared repository done everyday, but the frequency of integration is expected to be more than one integration. By this way, test activities are performed during every integration and problems caused by the integration can be minimized. As it is emphasized in this blog , CI says us as "pay me now, or pay me more later" . If we look at the history of CI, it goes back to extreme programming (XP) which advocates that there should be frequently code merged to master to cover unstable requirements of customer

Report: The State of Mobile App Development and Testing 2014

Mobile is in everywhere. If you want to be successful in your domain you need to put your business to mobile world too. Because the trend of mobile device usage is still and is going to be increased, people want to continue to use web application with their mobile devices while they are mobile. According to Flurry , leading domain in this trend is social media like facebook, twitter, foursquare and many others; and  the other popular domains are respectively utilities, entertainment,  e-commerce, games.  By SmartBear , a report about the mobile application development and testing is published. Let's look at what SmartBear does and how to benefit from this research the we can analyze the situation. SmartBear is software company, mainly focus on software development, software quality and system management tools. They have more than 10 famous products on the market. For software quality and testing, SoapUI, LoadUI and TestComplete are well-known tools. Based on my own exper

Selenium Chromedriver Error Message: u'unknown error: unable to discover open pages

If you use selenium webdriver to automate regression test cases, you may have got the following error. Because a bug in chromedriver version 2.3 causes this error. According to Google Dev ., this problem had fixed in version 2.6.  Assigning the chrome driver to driver leads to this error by the line 38, which is self.driver = webdriver.Chrome() . To solve the problem, you need to change the chromedriver version 2.3 in your execution path, like C:\Windows\System32 under Windows, with newer version. You can download chrome driver from googleapis .   Error message may like this: Traceback (most recent call last):   File "D:\workspace\automation_project\run.py", line 32, in <module>     m = Project(browser, server)   File "D:\workspace\automation_project\test_case_imps.py", line 38, in __init__     self.driver = webdriver.Chrome()   File "C:\Python27\lib\site-packages\selenium-2.35.0-py2.7.egg\selenium\webdriver\chrome\webdriver.py", line

World Quality Report 2013-2014 | Dunya Yazılım Kalitesi Raporu 2013-2014

Dünya genelindeki üretilen yazılımın ve yazılım süreçlerinin kalitesi belirlemek için Capgemini, Sogeti ve HP tarafından yapılan çalışma yayınlandı. Bu çalışma 2013 yılında yazılım kalitesiyle ilgili toplanan verilerin 2012 yılındaki çalışmada elde edilen verilerle kıyaslanarak bu alandaki değişimleri de bize aktarmaktadır. Ayrıca 2015 yılı için beklentiler hakkında bilgiler de vermektedir. Dünya genelinde yapılan bir araştırma olmasından olayı değerlendirme yaparken Türkiye'nin veya kendi firmamızın bu verilerin neresinde kaldığını görmemiz adına güzel bir kaynak olabilir. Araştırmayı değerlendirmeye başlamadan önce herzaman olduğu gibi önce araştırmanın kimler tarafından yapıldığını, bu araştırmadaki amaçlarını ve bu araştırma sonucunun araştırmacılara sağlandığı yararları belirlemek gerekir. Bu sayede araştırmanın kendimiz veya kendi firmamız için ne anlama geldiğini daha iyi analiz edebiliriz.  Capgenimi dünya genelinde 44 ülkede 130.000 çalışanıyla faliyet göstere

Yılın Yazılım Testi Hakkındaki Son Yazısı: Özeleştiri

2013 yılı biterken son olarak bu yıl içerisinde yazılım testi ile ilgili bazı noktalar hakkında yazmak istedim. Benim açımdan bir yıl boyunca neler gelişti, neler değişti ve ne gibi değişimleri 2014 yılında görebiliriz. Kısa kısa değinmek istedim. Testlerin başarını her zaman kontrol etmeliyiz. Zaman-zaman kendimizi özeleştiriye çekmeliyiz ve yapılan hataları, gözden kaçanları, eksiklerimizi tekrar hatırlayarak gidermeliyiz. Mesala mesleğe girerken veya bir süre sonra aldığımız sertifikalarımız uygulama aşamasında gerçekten sektörle ilgili yeterince bilgi ve beceri verebiliyor mu? Veya bizler bu sertifikanın verdiği bilgilerdeki eksiklikleri veya hataları bulabildik mi? Eğer sorulara "evet" yanıtını verebiliyor isek ozaman aslında doğru yoldayız diyebiliriz. Mesala dünyada en yaygın durumda olan ISTQB sertifikalarıyla ilgili bu linkteki açıklamalar hiçte yabana atılacak gibi değil. Sertifikayı veriyosunuz ama testlerdeki değerlendirme kriterleri, içerik, ve testlerin tuta

Jean-Claude Van Damme'nin Test Dunyasına Katkısı

Bu reklamı izlemeyen yoktur sanırım. Peki bu reklamda anlatılmak istenileni bir de test dünyası için yorumlamak istersek bize bazı noktaların önemi gösterecektir. Bildiğimiz Van Damme her zamanki gibi formunda ve yapılması güç bir şeyi yapıyor. İlerlemiş yaşına rağmen (1960 doğumlu ) bütün riskleri alarak böylesine izlemesi zevkli ve heycanlı görüntüler gerçekleştirebiliyor.  Peki burada sadece kahramanımız Van Damme'mi risk alıyor sizce. Cevap tabiki "Hayır". Böylesine meşhur olan bir kişinin başına gelebilecek bir ciddi kaza durumunda bu reklamla ürünlerini tanıtmaya calışan Volvo markasının aldığı risk sanırım daha fazla. Peki bu riskleri sıralayalım. Van Damme'nin ölme riski Van Damme'nin yaralanma riski Haberin Duyulma riski Markanın itibar/güven kaybetme riski Kar etmeme riski Yüksek bir tazminat ödeme riski ... Bu şekilde sıralandığında tabiki en önemli risk bir kişinin hayatı kaybetme riskidir. Testler sonucunda unutulan bir hatanın ku

E-Commerce and Testing

History of E-Commerce Doing trading something over the internet is simply called as electronic commerce, shortly e-commerce or eCommerce. The technology of e-commerce goes back to the 1979 when Micheal Aldrich introduced first online shopping system. Then Tim Berners-Lee used NeXT computer to create first web browsers and called it World Wide Web (www). When we came to 1995, the first e-commerce website amazon.com was launched by Jeff Bezos and later on the same year, ebay.com was launched by Pierre Omidyar. If we look at what happened this year, according to the b2b2dot0 which has gained this information from SAP-integrated eCommerce solution, for the 2nd quarter of 2013 the revenue is 147 Million dollars and 326 Million for 1st and 2nd quarters in total for only B2B market. According to the Forrester study prediction about 2013, 559 Million dollars for B2B market and 252 Million dollars for B2C market will be released.   Type of E-Commerce There are many types of selling

Internet Explorer is now More Helpfull

When you want to check if your site works fine on covered versions of Internet Explorer, you may need to check it via IE. Because most front-end developer, who are generally responsible of developing viewable part of site by users, uses Firefox or Chrome for base of development and then develop problematic part of it for the different versions of IE. This is called compatibility. This kind of testing called as compatibility testing or cross-browser testing is very crucial for e-commerce site because it can cause many customers stop buying, stop member record, or any money related big-bang-bug (bbb). Compatibility testing is a kind of non-functional testing which means that they should be run upon the functional testings have been completed. Actually, this means that there is very little time remaining for compatibility testing at most case. To complete this task there are several webs or tools which make some cross browser testing but I have not yet find a successful one. Since th

How to Use Internet Explorer and Safari for Mobile Testing

Have you recognized that everyone is mobile! And almost everyone socialize with mobile internet (this socialization doesn't mean to have sharing with anyone close to you, it means to chat/share/discuss online with anyone far to you). Since the ratio of using mobile devices are getting increased, needs for mobile testing is also increased. Many companies have developed mobile applications and mobile website to increase their customer satisfaction and to catch up with their rivals especially in e-commerce sector. In this post, I want to share :) some information how to test mobile application with your desktop. Mobile websites/applications target mobile devices but testing everything may not be possible with your devices, or not effective! For some test case like searching, defining cookies; checking links, redirection can be tested easily with your web browsers. For example, Apple's Safari and Internet Explorer can be used for mobile testing.  Safari : you must activate t

Combinatorial Testing

Combinatorial testing is a testing technique which is applied by combining the meaningful input as test cases. This method aims to reduce the number of test cases depends on the studies, which show that combinations of one value (one-pair) test cases can detect 20% to 68% of the defects; and combinations of two values (two-pair) test cases cover 65% to 97% of defects; and the combinations of more input values have higher defect-detection-ratio. If you remember the 7-testing-princible, I will mention two of them as “Testing shows presence of defects” and “Exhaustive testing is impossible”. These items explains that when we test an application we can only say that we have found these incidents which may be defect or not, but we cannot conclude that there is no defect remains in the system since you cannot find a %100 defect free application in the real world. What is more, testing the whole system including all part of the features and every line in the code base with every integratio