Better late than never :-)
I attended Agile Testing Days 2013 and went to India for holidays. I am back in UK now and it’s time to reflect on the conference and share my experience.
Agile Testing Days started with a great note - some of us went for dinner and many people stayed in the bar till morning. I was relaxed because I didn’t sign up for any tutorial for the next day. I decided to take a day off from testing and explored Berlin before joining others for dinner.
Opening keynote of the conference was from Andrea Tomasini. I found it extremely fast paced and packed with.. well a lot of information on what agile is. You can find my notes from the session here . Key takeaway from the session for me were the notion of social, technical and business risk in agile projects and reasons of dysfunction ...
For quite some time I was thinking of improving blogs / articles I have written on TestingGeek in past. Many articles I have written in past do not reflect my current thinking. However I decided to leave that exercise. May be it's better to show that my thinking ( and writing) has changed. I might re-write some of the articles and link them from the old articles to ensure that folks landing on my old pages have opportunity to see what I am thinking now.
However, this thought process was useful because I ended up thinking about the opposite - which blog posts do I like?
So here is the list of blog posts (In no particular order) I like on TestingGeek. You may have read some of them earlier, if not it would be nice to know your thoughts on them.
Testers journey from Manual to Political
This post was story ...
Test automation is an interesting activity. When teams start their journey, interesting things happen. Teams become more efficient, test coverage increases, communication between software testers and developers increases, fewer defects are reported by customers and so on, isn’t it? But does it happen every single time?
Let me tell you a story – BTW, all persons portrayed in this story are fictitious and any resemblance to living or dead, manual, automated or political tester is purely coincidental.
A small team of few developers and testers was working on a product at company X. Test team at company X wasn't experienced and lead tester of the team was Jim. Jim was a good tester. He was extremely good at finding defects - unfortunately he never got opportunity to work on the test automation projects. Management at company X had no interest in approach – they wanted results and they never pushed team ...
The word experience has become overused. What does it convey when you say I have 10 years of experience or 5 years of experience in software testing? Nothing.
Experience, in my opinion is a very broad term. Experiences in software testing could be physical, mental, emotional, religious and social.
If I recall my software testing experience, it’s a mixture of all of these.
Software testing takes the form of physical experience, when I compare product with the spec in any form. It can also take this form if I am doing it subconsciously. Few activities which fall under this category are
- Comparing UI elements on screen against design
- Sound produced by the application is not according to specs
- Application is not responding well to the touch screen gestures
- Application is not working as specified
- Creation of throwaway record and playback scripts
In nutshell, role of my brain is probably ...
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 ...