Mumbai: 12 Nov.2009 – 12 Nov.2009 Hyderabad: 16 Nov.2009 – 16 Nov.2009 Chennai: 13 Nov.2009 – 13 Nov.2009 Bangalore: 17 Nov.2009 – 18 Nov.2009
Course Description
Rapid testing is a complete methodology designed for today’s testing, in which we’re dealing with complex products, constant change, and turbulent schedules. It's an approach to testing that begins with developing personal skills and extends to the ultimate mission of software testing: lighting the way of the project by evaluating the product. The approach is consistent with and follow-on to many of the concepts and principles introduced in the book Lessons Learned in Software Testing: a Context-Driven Approach by Kaner, Bach, and Pettichord. In interactive workshop, Michael Bolton, the co-author (with James Bach) of the Rapid Software Testing course introduces testers, managers, developers, and any other interested parties to the philosophy and practice of Rapid Software Testing, through lecture, stories, discussions, and “minds-on” exercises that simulate important aspects of real software testing problems.
Contact Details
Bangalore/Hyderabad: Akshay Raj
(M): +91-9845176034
(P): +91-080-41574806/7/9
akshay.r@edistatesting.com, training@edistatesting.com
Chennai: Harsha Bhat
(M): +91-9845098916
harsha.bhat@edistatesting.com
Delhi: Divya Raturi
(M): +91-9871252501
divya.raturi@qaiglobal.com
Mumbai: Kishor Parab
(M): +91-9821251126
kishor.parab@qaiglobal.com
I have registered. When will you register?
Thursday, November 5, 2009
Golden Chance to meet Michael Bolton in India!!!
Friday, October 16, 2009
Three Years: Worth the wait?
Five Lessons Learnt from my last Testing project
1. Every project teaches you something new if you are ready to learn.
I tested a web based application for the first time. Introduced to terms like IISRESET, HOSTS, PROXY SERVER, RAD GRID, AJAX, HTTPS, DOMAIN NAME, DATABASE SERVER.
2. A tester's role is to meet the mission.
I found 73 bugs in 6 hours and had to close 69 bugs because they were not at all important from the customer's perspective.
Previous Project: Found 710 issues and 685 were fixed. Everyone appreciated me.
This project: Found 73 issues and 4 were fixed. Everyone asked me to concentrate on features which the customer would use.
3. Test on the expected environment.
Tested for two weeks on an environment which was not the environment at the customer end. Now I feel, why did we waste those two weeks?
4. Test the environment first.
Believed a technical person for setting up the environment and the environment was wrong. First build to customer and it failed miserably. Tested the environment and found that a simple mistake meant that we tested on the wrong environment for two months.
5. Work as one team towards one goal.
It is good to interact with programmers, product managers, tech support, sales manager, QA head, Development Head. Everyone has something new(read different) to contribute.
WOW, I'm very happy that after three years of testing in office, this is my first product release to market.
I'd say worth the wait for three years.
So, when's the next release BOSS? I'm waiting :)