Wednesday, July 25, 2012

Rapid Testing Intensive - Day 2

Today was the second day of the Rapid Testing Intensive.  Another interesting day with the Bach brothers (James and Jon).

Today we talked about Test Strategy, Risk Analysis, and Test Oracles.  We also got a lecture on Test Oracles from James, and a live pair Exploratory Testing exercise from Jon.  All in all, another good and packed day!

Today's pearls of wisdom by James:
  • Our job is not documentation - it is to get the testing done. Learn how to takes notes w/o interfering with your testing.
  • To train yourself to take notes, try setting a timer every 15minutes for a day. It will build in a practice of taking notes.
  • What should session notes include? Tell the story of your testing - briefly. For a 90min session, three paragraphs are enough or 10-15 bullet points. Tell enough so that someone can visualize what you did.
  • Oracles: A medium by which we connect our feelings about the product with the opinion of someone that really matters.  If they're not satisfied, you have a big problem.
  • Oracles: A natural tester just looks for inconsistencies. You have to be able to describe your testing. Oracles are heuristics; there are no oracles that are perfect. Oracles require ongoing learning.
  • Oracles: You're a tourist if you test with no oracles - you're just observing - that's lack of an oracle. You're touring a product. You're not testing.
  • James is nervous when not testing with other people because he's afraid he'll miss something.
  • Rapid Testing is rapid learning.  Learning is a normal thing that happens all the time.
  • "If you're confused, you're right on track"

Tuesday, July 24, 2012

Rapid Testing Intensive - Day 1

Today was the first day of the 5 day "Rapid Testing Intensive" by James and Jon Bach.  What an awesome experience to be able to learn from these two master Testers.  There are several folks onsite with them in Seattle and over 100 of us online from all over the world. 

They did not mess around.  We immediately jumped into things.  We started off with each of us working on usability testing and product familiarization on the Motors site on eBay.  It was a great way to get familiar with the product pretty quickly.  By all of doing this, 88 bugs were written!

James then took us on a high-level overview of Rapid Software Testing.   Here are some of his pearls of wisdom:
  • Rapid Software Testing is a way of thinking, a mindset.
  • There are no best practices.
  • Learn to test!!!  After 25 years of testing, James still says that to himself.
  • Testing is about discovering the invisible.
  • Don't trust when your brain says something is simple.
  • Test automation can't simulate what humans can find in unanticipated problems.
  • In order to control a system, you must have/make a model of that system.
  • A model is any idea, activity, object that represents another idea, activity, object to help you manipulate the real thing.
  •  The tester is expected to relate what they are doing to the business and explain why they are doing it. 
  • Alternate reading the spec and play with product: Read, play, read, play, read, play, read, play.....
  • Don't mind being confused.
We then did an exercise with TCO's (Test Coverage Outline), again on Motors in eBay.  We each had the choice of working on the following:
  • Interface element
  • Data element
  • Platform and variants
  • Business logic & flows
  • Oracles

I chose to make a mindmap of the cars data:


All in all a great, full day and I'm looking forward to tomorrow.

Friday, June 1, 2012

Ajay Balamurugadas' Testing Class


In a previous post I mentioned a 5 week (3 days a week) online Testing class I was taking by Ajay Balamurugadas, a passionate Tester from India.  Our last class was this past Wednesday and it was a great experience.  Not just to explore new things in my journey of self-learning, but to experience a Skype group class full of enthusiastic people from India!

Ajay’s passion about Testing and passing on his knowledge came through in this class.  It was evident in the beginning that he wanted the class to succeed.  He could be tough on you, but he would do it with a good intention to challenge you, to bring out the best in you. 

A few of the things we worked on, alone and as a group were the following
  • Test strategy
  • Mind maps
  • Test ideas
  • Bug investigation
  • Bug reports
But we also went off the agenda many times to discuss an interesting new topic or a question that came up.  That was always a fun adventure.

I was very interested in the discussion on mind maps.  I’ve done a little bit with them, but since this class they’ve become a bigger part of my life.  It’s an easier and faster way to break things down to workable bits than just making lists.  I’m finding that I’m not just using them for Testing, but for other things in my life.  The other thing that I’ve taken away from this class is Ajay’s enthusiasm with Testing.  It’s easy to forget that we as Testers really do love Testing when we are so busy and it sometimes feels like a “job”.  One of the best ways to conquer that is to continue to learn new things.  And there are so many ways to do that.  So many resources out there!

I’ve been a Tester for several years, but I couldn’t pass up not only a free class (thanks, Ajay!), but a class from someone I’ve been hearing about from other Testers and Testing coaches.  Experienced Testers (and new Testers) should take every chance they can squeeze into their busy schedules to get as much training and self-knowledge as they can.  You never know what new nugget you’ll hear about that you can add to your tool box but also pass along to other Testers.

I now consider Ajay to be a friend along with many people in the class.  A very nice perk!

Check out Ajay’s blog at www.enjoytesting.blogspot.com/

Tuesday, May 22, 2012

A *WEEKDAY* Weekend Testing Americas session this Thursday (5/24/12)

Agilistry Studios is hosting "Agile Up 4 Here" this week, and as part of their project, they have asked that the Weekend Testing crew hold a special session to beat up on their application they are developing. If you would like to participate, the details are below:

What: A Weekday Weekend Testing Americas Chapter Session (No. 28)

Session Type: Exploration, Bug Hunting

Date: Thursday, May 24, 2012

Time: 2:00 p.m. to 4:00 p.m. Pacific. Check in your time zone.


To join this session, please do the following:

1. Add weekendtestersamericas to your Skype contacts if you haven't already.

2. Fifteen minutes prior to the start of the session, please message weekendtestingamericas and ask to be added to the chat session. Once we see you, we will add you to the session.

For more details, contact:  WTAmericas@gmail.com

Monday, May 14, 2012

My Two First Weekend Testing Experiences


For those of you not aware, there is a group called Weekend Testing.  It’s exactly what it sounds like, doing some testing on a weekend.  The group originated in Bangalore, India.  The original name was Bangalore Weekend Testers but eventually evolved to Weekend Testing and now has groups in Europe and the Americas.  The mission is:  A platform for software testers to collaborate, test various kinds of software, foster hope, gain peer recognition, and be of value to the community.  Sounds like Testers to me!

My reasoning for doing this is to get more involved in the Testing community at large, keep skills up, learn new things, challenge myself, and get to meet some great and dedicated Testers from all over the world.

The first Weekend Testing event I participated in was with the Americas group on Saturday, May 5th at 11:00 AM Mountain Time.  I mention the time of day because the second event I participated in (which was Weekend Testing from India) was this past weekend on May 12th, but since it was originating from India…..it was at 4:30 AM Mountain Time.  Now, I’m a morning person, but needless to say, there was a nap in my future for Saturday afternoon!

I honestly had no idea what to expect since I had never done anything like this before.  I wasn’t sure how one joined and how it all worked.   To join and get involved, you do the following:

      1. Email either group and them letting them know you would like to participate:

          2. You will get an email from them, but basically at that point, you’ll want to add either group to Skype and request to have them add you as well:
            weekendtestersamericas
            weekendtesting
It’s really that simple to join.  They both meet once a month (but not on the same Saturday).  They will contact you to let you know when the next one is coming up and hopefully some information beforehand on what is going to be tested.  It’s helpful if you know what is going to be tested beforehand and to even think things through, because the more you can get things setup before the session, the better it will be for you. 

The morning of the event, you should bring up Skype.  People start saying hello a few minutes before the start time to each other and things get going pretty quickly.  If nothing else, it’s a great experience to do a group Skype.  It’s fascinating watching everyone asking questions, giving instructions, etc.
For the most part, it seems that what both groups do is take a function of a website and everyone tests that.  You test for about an hour either alone or in pairs or groups (seems that most do it alone because it is easier since everyone is on Skype).  

In the Americas group session, we tested more than just a function.  We were to test different versions of Wiki sites (Wikipedia, Wiktionary, Wikisource, Wikinews, Wikibooks, Wikiquote, Wikiversity, etc.), and do regression and exploratory testing.  Again, this was different than what they usually do, which is generally testing a particular function.  But this last Saturday in the Weekend Testing (India) group, we did do just a function.  We were to test a new function on eBay.  As someone that hasn’t been on eBay for over ten years, I must say I probably spent too much time in the beginning  just getting around the site, but I did find some bugs.

You should write-up any bugs you find along the way and at the end you can either email them to the facilitator or sometimes they have Bugzilla setup.  During the testing hour people can also ask questions, tell others what they found, and just have some general discussions.  At the end of the testing hour, everyone can ask questions, share their bugs they found, what their experience was like, if they had any challenges, etc.  The facilitator of the group takes a few days and prepares a report which they publish for all of us.  They will also send the report to the open source developers or project owners as well.

I would highly recommend for any Tester (rookie or experienced) to do this.  It’s always good to practice our craft.  Actually, it’s essential.  I must be honest and say that as a first-timer with Weekend Testing, both sessions really challenged me.  As I said previously, I’ve never done this before, which is why I really wanted to do this.  I realized that I’ve been used to having the time (even if it’s a half day) to think through what/how I was going to test something, and that was on the product I’ve been testing on for quite awhile.  This was great to go in cold and “just test”.  I don’t mind at all that I was challenged by this.  It was an eye-opening experience that I am looking forward to experiencing again next month!