Friday, December 11, 2009

Do you TRUST the fix?

Something interesting happened when I was testing with my team.

One of the team members had logged a critical issue.
It was a bit complicated too. It involved a lot of parameters to consider.

After a week, the issue was fixed and the team member who logged the issue was verifying the fix.

After quite a bit of regression testing, I heard an interesting comment:

"Amazing!!! I'm surprised how could the programmer fix this issue without any side-effects"

Hmmm, it so happens that we expect the defects to be fixed.
And when they are fixed, we start questioning.

It is good to question but questioning everything.... being so skeptical... I don't know.

Maybe it is good some times but not always.

Do you TRUST your programmer and his fix?

Let me know.

Leia Mais…

Touring and Modeling: Scripted Vs Exploratory

Discussions on twitter helps.

Fast, Open to public for views. Private (if required).

So, while discussing about software testing on twitter, more specifically about "Touring", "Modeling" with Shrini Kulkarni, some questions cropped up.

1. Is touring a way to explore a model in software testing?
2. Does touring happen in Scripted Testing? To what extent?
3. Does Touring happen more in Exploratory testing than Scripted testing?

Touring - a way to explore a model, is a continuous way to build a better model. Once a better model is built, a new tour to explore it in more detail could be carried out.

As mentioned by James Bach in "Exploratory Testing Explained",

exploratory testing is any testing to the extent that the tester actively
controls the design of the tests as those tests are performed and uses information gained while testing to design new and better tests.
So my question is:

We follow a restricted tour in Scripted Testing. In Scripted testing, our next test is not based on the result/information gained from the previous tour. Are we not following a strict roadmap or the touring is restricted?

Isn't touring and modeling a one time activity in Scripted Testing? A tour may be done to gain information to write the scripts.

In Exploratory Testing, isn't Touring and Modeling a continuous activity to gain more valuable information?

Are they both - "Touring and Modeling" in a loop in Exploratory Testing?

Final point: "Touring and Modeling" is restricted in Scripted Testing and "Touring and Modeling" is a continuous activity in Exploratory Testing.

What do you think?

Feel free to correct me, comment, discuss, question, argue and finally tour the model I have in my mind.

Leia Mais…

Saturday, December 5, 2009

Experience Report of Facilitating WT 17

Date: 05th Dec 2009
Time: 2.30pm - 5.30pm IST

Parimala Shankaraiah and myself were ready to start the session.
Yes, two facilitators to organize a testing session with nearly 25 registered testers.

And James Bach is on Skype waiting for any questions from the testers.

WOW... All set and what's this... I can't find Parimala online.

Beep Beep: Message on Mobile:
Powercut at my place
- Parimala

SOS sent to Sharath Byregowda and 2.25pm IST, powercut at my place.
Oops... Both Parimala and myself rush to the nearest cyber cafe near our home.

Both Parimala and myself login just in time from two different locations.
I started adding the new members for chat while Parimala took over the task of sending the email to those present on time.

Once group chat was initiated, we exchanged roles. I contacted James on twitter.

So with James on standby, Parimala on chat clarifying the questions from testers, I was sending email to every tester who had not yet received the email disclosing the details of the WT 17 session.

Half an hour and it seems that everything is settled.

Slowly questions started cropping up in the discussion.
Initially questions were re-directed to James on twitter.

Later, email id and skype id of James was given to testers for direct interaction. Thanks James for your precious time.

Literally, two hours just flew. Finally an email thanking the testers and highlighting the deliverables was drafted and kept ready. While testers were busy testing, Parimala was drafting the email and I was adding the new email ids to the list.

At 5pm IST, we sent out the email.

Testing was stopped at 5.30pm IST and reports were trickling in since 5.15pm.

Surprise element: There was last minute change in the specifications and those who asked James about the specification got more details.

Only the testers who asked questions got to know more information...

Questioning: Very important skill of a tester.

Finally, all the reports came in by 5.45pm.

Parimala and myself logged out to have our lunch :)

Thank you Weekend Testers.
See you in next WT session .

Leia Mais…