If you are involved in doing any kind of test automation for web application, I am sure you are either using, or have considered Selenium for your test automation efforts. Well, if you have not considered, then maybe it’s time to give it a shot…

For folks who are familiar with or are using Selenium / WebDriver in any form, I hope you are aware that Selenium conference is happening from 16’Th to 18’Th April in London.

Last year, I travelled all the way to San Francisco from London to attend the conference and presented Magic of Modular Test Automation and this year I am presenting One Step At A Time (Will publish slides after the conference). BTW, I also wrote laziest experience report of Selenium Conference 2011 to share my experience … and to summarize my last year's experience in one word - Selenium Conf 2011 was AWESOME ...

Continuous performance Monitoring

Performance testing is an important and integral part of most testing projects. This type of testing corresponds to Q4 of the Agile testing quadrant. You can find interesting insights on the agile testing quadrants in this post by Lisa Crispin.

Usually performance testing teams are different from functional testing teams and their reports / data etc are not easily available to to the entire team. I wanted to have more visibility, integration and feedback about the performance of application - essentially I was looking for Continuous Performance Monitoring.

In this post I will discuss what is continuous performance monitoring and how useful it is to report performance trends for every build.

In my current project, I am using TeamCity as the build server. TeamCity supports custom charts for any data. I thought, It should be possible to have performance data from all the teams in a particular format and ...

I attended weekend testing America’s session number 18 on Saturday. It was my first WTA session and I must say it was a good learning experience. There was an interesting exercise given by James Bach. The exercise was about Test Charters.

As part of the exercise, we had to critique existing test charters and improve them. I went through the definition of test charter given in the exercise to understand more about test charters. I tried to critique and improve the example charters, based on the definition given in the exercise. I was not satisfied with the outcome and wanted someone to critique my (improved /modified) charters.

My (improved :-)/modified) test charter was discussed during the briefing session and Michael Larsen , Wade, Shrinik and Lalit gave interesting feedback on my charter. During that briefing session, I realised that I can draw analogy of writing test charters to writing user ...

Software testing is a relatively new field and has changed considerably in past few years. It is not taught in many universities and when I moved from development to testing in 2001, I was confused about it. I tried to learn from internet, books, forums and was not impressed with the information I got. I even did my certification (CSTE, if you are interested) but that wasn't very useful either. During that time, I came across many interesting theories / concepts and after working in the industry, I know they are not true, and are myths. Unfortunately, some of these myths are still in practice and widespread.

Myths in software testing has done this field more harm than good. In this post, I will explore popular software testing myths, why they are myths and what wrong these myths are doing to our profession?

1. Testers are Gatekeepers Of Quality - Nothing ...

Web applications are everywhere and most of us test them to earn our bread and butter. Broadly speaking, there are two types of web applications or websites - One which provide service and another which provide content. Web applications such as emails, facebook, bank or blogging platform provide a specific service and BBC, Times and many such sites provide content.

Irrespective of the type of web application, all of them need to understand user behaviour on the site and gather key usage pattern. One common way of doing this is with the help of analytic code. As a tester, it is important for us to understand how it works and how it can be tested. In this entry, I will discuss this in more detail and show you how iCheckWebsite can be used to test analytic code.

So what is Analytic code? Analytic code is usually a java script snippet which ...

Last month Komal Joshi and Patrick Martin presented @ GTAC 2008 conference in Seattle, USA. Google Test Automation Conference is one of the best conference for testing / automation and it was certainly a good experience for TestingGeek to present this at GTAC.

This presentation will give you basic information on how simple tools like SVN, batch files and task schedulers can be used to create Continuous Integration for mature desktop applications.

Solution like these are one of the best way to move teams towards more mature continuous integration environment. Using this approach, teams can start to see and appreciate benefits environment like this will bring to the projects.

Hope this presentation will be easy to follow and you will understand the basic concept behind this. Please subscribe to our newsletter if you want to remain on top of whatever is published on TestingGeek.

Rick Mugridge, Author of the famous book "Fit for Developing Software" explains the concept of story driven development, executable specifications and FitNesse. In this presentation, he addresses four main issues involved with software development and how FitNesse can be used to address following issues

1. How can we improve test coverage on a legacy system without discouraging its evolutio
2. How can QA be involved earlier and more effectively?
3. How can product managers better utilise their expertise?

Testing Mobile Handsets with FitNesse - Uffe Koch & Mark Boxall

In this lecture process and problems associated with developing mobile applications is discussed. Specifically, what kind of problems are associated with testing mobile applications, what type of test cases you need to write for mobile applications and how FitNesse can be used for mobile applications testing.

User story is one of the primary development artifact for the XP project teams. A user story contains just enough information so that development team can reasonably give estimate about completing, tester can discuss how it will validated and customer can see its value.

One of the common question that we hear most of the time is, how user stories are different from use cases. User stories are much simpler than use cases. User stories are very easy to create, discuss and develop. They also do not contain any technical details.

Typically good user stories are defined in the following format

As a I would like to do so that

While discussing User Stories, you should make sure that they are not very big. A big user story leaves the chances of ambiguity and absence of clarity in the mind of development team. Ideally, you should be able to break ...