Skip to content

Experience at Bangalore Testers Meet-up #4

It was 0600 PM evening at Bangalore on 28th, August 2010. It was cool climate, looked like it will rain but rain was in favor of our meet-up. At 05:30 PM some of the testers were roaming in forum mall [The venue] and then at 0600 PM we were at Transit in 2nd floor. I was glad to see call from Shivakumar who is a tester from Chennai accompanied by his co-testers. So, this time we had 3 testers coming to Bangalore all the way from Chennai for meeting testers and interacting with them. We just started with some introduction talk while we were waiting for other participants to come. When we had the entire known participants list that had come we started discussions and after some time Pradeep Soundararajan took initiative of starting an exercise. We had 3 laptops and there were 11 participants. So team was split up into 3 [2 teams with 4 members and 1 with 3].

Testing begins,

We were asked to test Microsoft Calculator. My team included, Dhanasekar S – Myself – Nitin Purswani – Shivakumar Mathivanan. I took the control of the laptop where I perform tests which include my test ideas and my team members test ideas. While we were testing Pradeep offered us drink and he got a drink for each of us. Finally, we got 10 issues [Wait, this wasn’t a competition this was an exercise]. We were asked to stop testing as the time got over.

Evaluation begins,

Pradeep Soundararajan started evaluating our reports and asking us questions about strategy – team work, individual contributions to the team and more. He was evaluating based on our answers and our reports and many other criteria.

Traps,

-      We did not ask any questions

-      We did not have a planned strategy

-      We just jumped on to testing

-      We just listed issues – We did not take down notes and our observation

I had a lot of learning at the end of Bangalore Testers Meet-up #4. Later, we had dinner and left to our home. Now, we are waiting for next meet-up. Want to join us? Then keep yourself updated by following me @santhoshst on Twitter or contact me at +91 98865 46088 to know more about it.

Thanks for your time in reading this blog post and I hope you are ready for the opportunity at next Bangalore Testers Meet-up. Happy weekend.

Bangalore Testers Meet-up #4

We are happy to announce that we will be having Bangalore testers meet-up on August 28th, 2010 which is Saturday. Without further ado, let us share the venue details and time etc.

Venue: 2nd Floor, Transit, Forum Mall – Koramangala

Time: 0600 0200 0600 PM IST [ We are back to 0600 PM IST - Sorry for inconvenience ].

Registration: No registration | anyone and everyone is invited

Food & Drinks: Spend from your own pocket :)

Contact: 9886546088

Twitter: @santhoshst | @ajay184f

Let your colleagues and friends know about this meet-up. Do not lose this opportunity and good news for you is you will have this opportunity monthly as we conduct this meet-up every month during weekend.

I hope you would make it.

Cheers!

uTest Q3 Bug Battle Experience Report

Overview

August 6th, the battle began between 23,000+ testers from uTest community. And this time it was between 4 Job Portals. They were SimplyHired.com, Indeed.com, and CareerBuilder.com & Monster.com. I was aware of only Monster.com – Famous in India apart from Naukri.com. This time there were few changes in the rules, 5 bugs per test cycle and if someone exceeds it then they are disqualified. So there were 5 test cycles, 4 for web and 1 for mobile – So totally a tester can log a maximum of 25 bugs but, it is Quality that matters and not Quantity. This time I had some changes done in my reporting style. It was precise, concise, & to the point. In my reporting style this time I have included information like Tools that I used in my testing activity to facilitate learning to the readers of my bug reports. The video reports were also of less duration – This is learning for me because developers have less time if they are under pressure to have patience to download a huge file and watch the video. I have noticed few things in past bug battles and this bug battle as well – Testers have to remember that attaching video or screenshot is context dependent. If previous winners had video reports attached it doesn’t mean it is BEST PRACTICE – Remember that there are no best practices. There can be good practices for a specific context. Suppose, a bug which can be understood faster by just steps to reproduce need not have video file or a screenshot attached. A bug which can be a GUI or something or you feel that steps to reproduce might not convey a proper message then you can use screenshot attachment. And video if steps are too much or there are different scenarios that you might want to cover to provide coverage on a specific module. So, testers have to learn to be context-dependent than more of process dependent or follow so called best practices even if they do not make sense in particular context.

Note to non-testers who participated or will participate in uTest Bug Battle in future,

  1. Learn testing – You might not know what is a bug and you might think something as a bug and report it.
  2. Learn from others bug reports – How to report? What to include in the bug report? And other information.
  3. Read Tester Help Topics – Do not hurry to participate in projects if you are not confident as it might hurt your rating.
  4. Participate in uTest forum discussions and learn from your fellow members

The above information I am providing because I saw few bug reports which did not convey any information about the bug. May be, the one who wrote that report understands but it is important to understand who the intended readers of bug report are. One of the bug reports which I saw was just one liner for every field that was in the bug report. Please read my blog post about Bug Battle is not about just steps to reproduce – Search for it at uTest blog.

Was I under pressure during this Bug Battle?

Yes, I was as I did not participate from the 1st day. Most of the testing activity that I did was on Thursday and during weekends. I took a lot of time to find quality bugs. I had a filter set for which to report and which not to. Remember that this is not just who reports maximum bugs. Please read the guidelines and follow Bug Battle discussions at uTest forums.

How many bugs did I report?

Till last hour I reported bugs and I reported 19 bugs totally.

Did I participate in Mobile test cycle this time?

In all my previous Bug Battle participation I did not participate in Mobile test cycle. But, this time as I had learning about Mobile Application Testing I jumped on to the test cycle and rocked it. But, I experienced little bit problems in taking screenshot or video from my mobile phone however, this problem made me to explore new tools which can better my testing activity in mobile test cycle in uTest projects and uTest Bug Battle.

Did I spend more time on reading the bug reports of other testers?

Yes, I always do this and it helps me learn and I love experiences – No matter how well or bad they are, because I believe every bad experience is a good experience to learn from it.

Could I have found more interesting bugs than what I did?

Yes, I would have found more interesting bugs if I had started my participation at early times however; I have still found interesting bugs with URL re-direction vulnerability, Brute-Force vulnerability and others.

What tools did I use & what resources did I refer or what did I learn in this Bug Battle?

  1. Perlclip [ Download available at http://satisfice.com/ ]
  2. Camstudio – Video capture
  3. WinZip – To compress in order to upload to uTest platform
  4. XSSed.com – More learning about Cross Site Scripting
  5. Learned more about bypassing captcha

Suggestion to uTest crew

I felt that 25 bugs are very much. 20 bug-limits is good enough. However, 5 per test cycle are good enough. I hope you take this into account however; I would want to take what others say about this.

Feedback on Job Portals

1st Place – Monster.com – Good GUI – More features – Easy navigation – More members

2nd Place – SimplyHired.com – I liked their style of concluding error messages

3rd Place – CareerBuilder.com – Good one – XSS restriction message – Cool

4th Place – Indeed.com – I liked Publishers thingy



All the best for your next Bug Battle while you are awaiting for results :)

Cheers!

My experiences about Myths

By looking at the title of this post you might feel that you know already about myths about Software Testing. This post contains myths that are covered in other blog posts also but I felt like writing it so I am. These myths have been experienced by me.

#Experience 1

I was coming from my organization in my cab and I sat beside a HR and the conversation when like this,

HR : How is your work going on?

Me : It’s going good

HR : Try to get into development

Me : Why do I need to?

HR : Testing doesn’t have growth

Me : What growth are you talking about? Money, Designation or what it is?

[ I explained him about testing and my passion towards it and said him that not to misguide people without knowing about testing ]

[ HR after listening to me ]

HR : Wow, I did not know about all this

Conclusion : There are many people who think they are guiding but they are misguiding, you can see that a HR doing it but I am glad that finally I made him understood and I hope now he won’t do it with any person.

#Experience 2

I met a tester before few months and there was an event and after the event he said me that he will be doing higher studies. And I asked what after higher studies, he said he wants to be in development. I asked why development? He said that his relatives whenever they come to his home they ask what is he doing and he says that he is a QA and they say Oh QA’AAAAAAAA and now because of his relatives talking like that he wants to do his higher studies and be in development. Now, you might be interested to hear that this was the same guy whom I had met before meeting at this event and he said that there are testers in his organization who open eclipse and do something to show that they are ready to move to development and this guy was complaining about them. Now, my question is, how this guy is different from those now?

Later, he said that he wants to follow money that’s all. Wherever there is money he wants to do that.

[ I just kept quiet and said good bye to him ]

Conclusion : Do not allow others to control your life. Sometimes what you think interests you might be because that is in your mind because someone else talked to you about it and you got biased.

#Experience 3

Before few months a fresher called me and asked me that in which institute I did my course in testing. I said there are no good institutes in Bangalore which teach you real software testing and they are just making money with those slides which doesn’t teach anything and they give you big material which consists of definitions. But they provide placement and every fresher wants this and doesn’t want to learn software testing [ Very few of them think about their learning ]. I asked that person why do you want to get into testing? And his reply was,

>> I do not like coding, that’s why I want to do testing <<

[ I became little bit angry but I took patience to explain about the myth that he had ]

I said that if he does not like coding and if he thinks testing doesn’t involve coding then please do not do it. But, as he was a fresher he might have those myths because someone else might have misguided him.  So, I explained him about testing and the conversation was over. I asked him that I would coach him for free and he said he would get back to me but he did not get back to me. After many months he calls me and tells he did his course in so and so institute and asked for my help to get me a job.

Conclusion : Testing involves coding / scripting. Writing your own tools to aid in your testing activity and also help the community by providing the tools that you develop.

#Experience 4

Most of the testers that I meet ask me a question like – Do  you know any institute where they teach QTP? I ask them why QTP? Some organizations are looking for testers who are good with QTP that is why they want to learn QTP. In this context, I am not against QTP but, what happens is some of the testers like this do not know to think, apply ideas, explore and they just know QTP and hiring these kind of testers might be a huge loss to an organization.

Example : Some test can be performed with a simple utility which is of very less file size in kilo bytes. But, QTP testers do not know about the utility which can do it and he / she knows how it can be done with QTP. This tester has QTP corrupted on his / her machine. Now, QTP installation has to be done and this QTP tester keeps waiting till installation gets completed now you see if he / she had known about that utility then a lot of time could be saved and huge savings to organization. I am okay with a tester who knows QTP and has skills to explore and can do a better testing but just a scripted tester is what I do not like.

Conclusion : No tool is a god tool. Everything is about context-dependent.

Do you read books? Do testers know about good books?

Most of the software testers do not read books – Why? They do not have time? Or they think reading won’t help [ Yes, certification books doesn’t help ]? Or some reason that they also do not know about what it is?

I always suggest testers to read books and I get different answers and here are few,

Investment on Books,

Me : Buy this book

X : Hey, if you have that book please give it to me for few days

Me : I suggest you to invest your little money on book instead of borrowing it

[ Finally, some end up in buying the book and some in not buying that book ]

But, still I do not stop from suggesting to other testers. I hope someone might buy and read them.

One more story from Landmark, which includes a book store [ Bangalore ]. I visit Landmark often and go near the rack of Software Testing [ I just get pulled there, I do not know how ]. I see some testers just buying books related to certifications and no one knows about good books [ Say Lessons Learned in Software Testing ]. I do not mind to invest my time in explaining to someone about good books on Software Testing. When people are near that rack – I ask them are you a tester? Then if they say, “Yes” then I talk to them about certification and good books and some turn up buying the book I suggested and some do not listen and just go ahead with certification books.

In Software Testing, there is endless learning – Your learning is not restricted to anything. Reading books like Lateral Thinking – By Edward De Bono and many other books – Reading different books helping you to build your vocabulary and what not?

Few books for you to buy and read

  1. Lessons Learned in Software Testing – By Cem Kaner, James Bach, Brett Pettichord
  2. Testing Computer Software – By Cem Kaner
  3. Are your lights on?
  4. General Systems Thinking
  5. Lateral Thinking – By Edward De Bono
  6. How to break Software?
  7. Nassim Taleb’s book The Black Swan [ Thanks to Abrahan Heward for pointing the missed out ]
  8. The art of Software Testing – Glenford J. Myers
  9. Perfect Software and other illusions of testing – by Jerry Weinberg

These are only few books that I know about but you can read other books and provide reviews on them through discussion forums, blogs and etc.

Educating testers and fresher about books,

If you know about good books that can help your friends or colleagues then please feel free to share it to them [ Example : I talked to one of my cousin about Software Testing and books that you he can refer to and kind of exercises he can do and he was impressed – He just passed out and he was referred to good resources and was guided properly, so how about you doing it ] . You might be responsible for a good change in the community. Write blogs and educate the whole world about books. Just keep spreading good things in this world.

Thanks for your time in reading this blog post and I hope this would have bought little bit change in those minds who were not reading books. If you need more details or you are not convinced then you can write to me at Santhosh [ dot ] Tuppad [ at ] gmail [ dot ] com