A Testers Journey

An ounce of practice is better than tons of theory

Get out of your comfort zone

After having spent my first couple of years in a very comfortable zone, things got really boring as day in and day out I was doing the same thing again and again. I started to think if I am stuck in my current role as a tester and will be stuck doing the same thing through out my career. First thing I did was to google for future of testing and after reading some 100+ articles I started to think if testing was my interest at all.

This is when I first stepped out of my comfort zone which is talking to people within my organisation, outside my organisation, in software, outside software, etc. I got a chance to meet and talk to some wonderful people and the following were their inputs

a. Start reading books, start with any books (not fictional or any novel) see what successful people have done and successful companies have achieved

b. Attend events which are not of testing

c. get to know of products which are not related to testing.

d. Check what you have done in the past for which you have got recognition and you enjoyed doing

e. Read and write blogs

Screen Shot 2017-07-13 at 5.48.46 PM

This search made my thought process and vision wider and I started to explore moreout of my comfort zone,

i. Worked with a not for profit org and hosted my very own testing conference

ii. Volunteered for UX, Mobile development and many other development related events

iii. Did my MBA in correspondence from Symbiosis

iv. Had my own website to write about Chennai and interesting things happening in Chennai.

v. Started exploring lot of products and started using them to understand them and what problem they were actually solving

vi. Jumped from a very big organisation to start ups

vii. Jumped from product company to services

vii. Got into product management, Delivery and Project management apart from heading the QA

If you are confused about your career, about what you are doing I strongly recommend you to get out of the comfort zone and understand your need and would enjoy and take that risk of even changing your career.

Advertisements

July 13, 2017 Posted by | Uncategorized | 1 Comment

Do not overlook issues reported by your users

There were many instances where the Ops, dev Team and some times even the testing team would overlook issues and pains reported by their users,We have got so used to using an application we would even know where and how an application will break and will not.

This assumption about the application has been one of the many reason for a buggy release. Also there are instances where the issues reported by the client are often overlooked or assumed that the client has done something wrong.

A typical line said by the ops, tester or developer when a bug is reported by a users are:

  1. Has the client anything weird, it has been working all these months / years
  2. Has the client using the required configuration in which the app will work
  3. This might get resolved when we send out a release later this week. etc etc..

Our first reaction is to blame the user as we are very protective of our app, our code, our testing etc. However when we put ourself into the shoes of the user and understand the reason for reporting this to us, we will start making better products and better releases

The customer is least bothered if you use the latest technology or the worlds top developer, at the end of the day if they are able to achieve what they wanted to do with your app is important, else your users would be looking for other options

 

 

 

 

July 12, 2017 Posted by | Uncategorized | Leave a comment

Test Plan latest version

I remember writing and reading pages and pages of test plan documents and managers running behind stake holders to update the test plan.

So this blog is going to help you create a test plan which can be maintained easily and also easily consumed by your team.

Step1: Identify the product for which you would req to write a test plan.

Step2: Split the application into features. There could be multiple features and sub-features in a product. It is your choice on how you want to categorise the features in your application

Step3: Rank (1-5) each feature in terms of their priority for the application.

Step4: Write the approximate number of test cases expected in each feature

Step5: Rank (1-5) the risks number for each feature. This is done based on the impact when a feature in the application fails

Step6: Create a mind map of test environment to be tested separately.

Step 7: Other information which is not applicable to the product can be written separately or in combination with Step 6.

Here you go !! Your test plan is ready

Couple of mind maps and a table and voila we have a test plan which can be easily consumed by any of our team member

 

 

 

July 3, 2017 Posted by | Uncategorized | Leave a comment

Bug-de-bug The Testing Conference

After few initial rounds of discussions on the feasibility and possibility of having a testing conference in Chennai with the RIA-RUI team the Bug debug Conference was decided to happen on Jan 29 2011 which was less than 50 days from the day we decided. Bug deBug is a conference By The Testers, For the Testers and of the testers. This event was initiated by the Chennai Software Testing Group and supported by RIA-RUI.
The main aim of having a low cost conference was to make technology available to all and make everyone understand the importance of attending conference, interaction and networking among professionals and freshers who wants to know about testing and learn as much as possible. Thus was born Bug deBug a conference organized by youngsters and passionate testers.
The registrations started at 9.00 a.m where the participants where given a participation kit containing a folder, notepad, pen, puzzle and brochures given by the event partners. The event was kick started at Sharp 10.00 a.m with the Master of ceremony Mr.Ananth saying “Not all conferences will start in right time and this is not among them”.


The key note speaker for the event was Mr.Vipul Kocher, President, Indian Testing Board. Vipul had his presentation on “Present problems and future solutions” his views on this topic can be seen here http://www.slideshare.net/riarui/bug-debug-keynotepresentproblemsfuturesolutions204. The session was very interactive and the entire crowd of testers where throwing questions at Vipul and had a very active start.
Following vipul it was Narayan Raman who presented on the topic “Economical, Robust Web Automation using Sahi”. Narayan highlighted the ease of use of Sahi and compared Sahi and selenium with their respective pros and cons. This was followed by a detailed demo on sahi which made understanding of the tool much easier and interesting. Detailed presentation of sahi can be seen here http://www.slideshare.net/riarui/narayan-raman.
After two continuos presentation there was a break of 20 minutes for tea and snacks which gave a chance to all the participants to interact with testers from other organization and also with Bug deBug speakers. Many participants who wanted to meet renowned testers in India had a chance to do so during the recess period. After a refreshing break Ananth announced various competitions which was available during the event.  The competitions were ,
1. Best Testing Tip

2. Good Question Contest


And also as a social cause Bug deBug collected money for chandru a tester ailing from Blood Cancer. Pradeep requested everyone to donate liberally for this cause. The team has a separate box for Chandru doing its rounds during the event.
The next session was of Pradeep Soundararajan. Pradeep presented on the topic “Notes from a problem solving tester consultant”. Which was very cheerful and had the entire crowd was roaring in laughter. Many testers questioned him on various problems. Pradeep linked testing with cricket analogies which made the entire presentation much more interesting. More information on pradeeps presentation can be seen here http://www.slideshare.net/riarui/notes-from-a-problem-solving-tester-consultant.
The final presentation for the morning session was that of Ruturaj Doshi who presented on “smarter ways of doing Selenium Automation(Functional Test Automation)”. Ruturaj stressed on automation starters using selenium IDE which is a firefox entension and went on to explain the pros and cons of selenium and its uses. Many testers who wanted to start with automation were keen on talking to Ruturaj after the conference. More information on this presentation can be found here http://www.slideshare.net/riarui/smarter-ways-to-do-selenium-automation-work.
After a heavy biriyani and sandwich, people took time to put in more testing tips in the board and also network with many speakers. One could see testers around every speaker trying to get their doubts clarified and trying to extract more answers to their questions.
The first session after lunch break was on “The Emerging Trend of Cloud Computing and Software Testing” by Anuj Magazine where Anuj spoke on how one can use cloud as a source of test environment and how when planned properly testing on cloud is cost effective. More information about this presentation can be found here http://www.slideshare.net/riarui/the-emergence-of-cloud-computing-and-software-testing.
The next session was followed by  Ajay Balamurugadas on the topic “I am the Bug Hunter”. Ajay’s presentation interested many freshers as they wanted to know how they can learn and make testing their career. Ajay also highlighted that assumptions are bad for any tester. Instead of assuming, when we question more on the topics where we have doubts one would have more clarity on the task to be done. Ajay instead of talking in the podium got down and was walking among the audience and answering questions put forward to him. This kept the audience more alert after a heavy lunch. More information on Ajay’s presentation can be found here http://www.slideshare.net/riarui/i-am-the-bug-hunter
After again breaking for a recess Ananth gave a final announcement for putting up testing tips and started of with the next presentation by Praveen Singh on “Testing at Startups”. We could see many participants from start-up companies very much interested in this topic. This topic also kept the freshers informed on how a testing cycle might be in start ups. Praveen stressed on what happens to a tester when his skills are low and one does not do anything to improve it. More information on this topic can be seen here http://www.slideshare.net/riarui/testing-at-startups


When the announcement was made that the best Testing Tip would win a prize we could see the testing tip board full. The best tips were taken from the board and selected by the speakers and 3 prizes for the best testing tip was given. The next contest was a raffles where participants had to do a puzzle and tear the bottom part of the puzzle containing their name name and emai id, winners were choosen randomly and ria-rui bags were given as prizes. Prize money was given to winners of online testing competition which was conducted in 99tests.com. The winners are 1st Place: Sudhamshu Ailineni , 2nd Place: Deep Verma , 3rd Place: Krishnaveni.
The most interesting and interactive session in the event was the Q&A session where all the speakers were asked to sit on the podium and all the participants where free to question any speaker. The best question or the question which was answered by more than two speakers were awarded fabulous books like Lessons Learned in Software Testing and Six Thinking Hats. This session took many by surprise as none of the conference had given the liberty to participants to ask questions for one full hour.
Finally the event closed down with the organizing team thanking the speakers, participants, volunteers for a very grand and successful event. Finally the team behind Bug deBug and its volunteers were introduced with of course lots of camera clicks.

I should also take this opportunity to thank RIA-RUI who gave the support to make this dream come true in chennai. RIA-RUI is a Society for “Rich Internet Application” – “Rich User Interface” a not for profit organization promoting congregation of ideas & knowledge in the field of RIA and RUI. The society is working hard to bring high quality technical events to India by partnering with local and international organizations for the benefit of the local technical community and students.
Ananth, Bala, Sathish, Karan, Umesh, Jackson and Bharath make the core team of Bug deBug. This team had penned down all the detailed tasks that has to be done and taken care that the team did not have any major work just before the conference.

Thanks to the volunteer team who were a great support and were with us all the time. Hearty thanks to Venkatesan Kannan, Sakthihasan kannan, Krishnaveni, Amudha Saravanan, Praveen Kumar Cherukuru, Parthiban Palanivel, SelvaPrabhu Palanivel, Subramanian Anantharaman, Raghavendran Narayanan, Anandakrishnamurthy ramasamy, Gopalsamy kannan, Narasimha Reddy, Vinothkumar Ganesan, Santhanakumar vivekananthan and Ravi Surya. If I have missed anyone i am are really sorry and it is not intentional (Put a comment to get your name added).

February 3, 2011 Posted by | Uncategorized | 2 Comments

Software testing conference in India – Bug deBug Chennai

After the successful event of Flash Camp Chennai, RIA-RUI Society is now targeting the community of testers. The conference is named as “Bug deBug” and the event is scheduled on 29th January 2011. This event is organized with the help of Chennai Software Testing group.

The society is branding “Bug deBug” as a platform for testers to meet their fellow testers, network / share / learn / evangelize. Bug deBug is a place to meet community champions and experts from the testing industry in India. Bug deBug is also a place to showcase your product / service / tool related to testing and get expert opinions.

Chennai Testing Conference

January 13, 2011 Posted by | Conference | 1 Comment

Experience with usability testing:

Experience Report on usability testing:

Off late we have been designing a new application and when we were almost ready, my team wanted to see how effective our application is to the real users, so we did a usability testing and I was part of it. 

Usability Testing:

Usability testing is to test our application in the following aspects,

Learnability: How easy is it for users to accomplish basic tasks the

first time they encounter the design?

Efficiency: Once users have learned the design, how quickly can they perform tasks?

Memorability: When users return to the design after a period of not using it, how easily can they reestablish proficiency?

Errors: How many errors do users make, how severe are these errors, and how easily can they recover from the errors?

Satisfaction: How pleasant is it to use the design?

Ref: http://www.infodesign.com.au/ftp/UsabilityTesting.pdf

Let me now share my experience on usability testing,

Steps followed before commencing usability testing:

1.  First the environment for accessing the application was obtained.

2.  Then the purpose of the application was learnt and the end user was known.

3.  Did some exploration of the application and learnt how to use the application.

4.  Questioned myself and the user on things to be done,

– Before starting to test.

– While doing the testing process.

– After finishing the testing.

5.  Learnt to use a tool used for recording the user actions and for calculating the time taken.

6.  Ready for performing usability testing.

How the usability testing was done:

1. The end users were asked to come to the location.

2. Each user was tagged to one volunteer who would help the user in doing the test.

3. Before the user started to use the application

– The application was kept ready along with the input data sheet.

– The recording tool was kept ready.

4. The user was briefed on the following,

– The reason why the user has been called.

– About the application and

– How to find things and use the application.

5. The user was also told that all his / her actions were recorded and the reason for recording.

6.  During the course of testing any doubts raised by the user was also taken care of.

7. After the testing process the users were asked their feedback about the application (Verbally).

Things learnt from this process:

1. Knowledge about the application should have been more.

2. Briefing about the application should have been discussed among the volunteer so that the end users are given the same knowledge transfer.

3. It’s important for the user to stay comfortable.

This our usability testing on our application was done, I would like to get more feedback and suggestions on usability testing.

DISCLAIMER:

All the blogs shared by me are my ideas, my thought, my understanding of the subject and does not represent any of my employer’s ideas, thought, plans or strategies.

April 28, 2010 Posted by | Uncategorized | 3 Comments

Skilled Exploratory Testing

Skilled Exploratory Testing

Skilled Exploratory Testing this is the first testing workshop attended by me . This happened in Chennai – March 27 and the speaker is none other than the highly spoken Pradeep Soundararajan.
We started off with few basic questions, like what is testing ? Immediately came the answer, to check if the application meets the requirements. Something simillar was answered by everyone in the workshop without questioning or thinking.  After waiting for everyone to answer The next question shooted at us was, what is software testing ? This made me think infact laugh at my self when i gave the answer assuming testing means software testing. This was a message i got that there is no assumption while testing a software.
After this few other questions were ,
1. What is manual testing ?
2. What are the deliverables of a tester ?
3. What value does a testers add to a team ?
4. What value does a team of testers add to your project ?
All questions had n number of answers from n number of people. This proved what a mess we are in with a single question having so many assumptions by so many people. All the above questions are real good examples to prove the importance of questioning. Testing without questioning and based on assumptions may prove fatal was the first learning at the start of the workshop.
Next in line was how testing and checking make a difference to the growth of testers. Checking is a something which can be automated and which does not require any human skills and brain whereas testing requires human skills and test ideas to be generated. Its painful to know that some companies recruit test engineers to check their product by giving check cases which mentions even the micro details thats seen when the testers navigates in the application, thereby limiting his/her learning and exploring capabilities.
After a initial set of discussions we had a few exercises in finding bugs :). The moment we hear the word find bugs what do we do ?? …. Yes you are right, open the application and start testing and this is exactly what i did.  Now whats wrong in doing this ?
The following might be the problems that could be faced,

1. Not paying attention to the full requirement might make us not achieve what is actually required and we would end up wasting our time.
2. Not questioning the requirement, for example we might be testing a product not knowing who the end user is, which again is a threat to release the application.
3. Not spending few minutes to understand the application.
4. Not exploring the application for clues or logs that could help us in testing.
5. Not thinking out of the box for test ideas and planning the testing activity.
And many more…
What I learnt after the testing session ,

1. Difference between Symptoms and Problems.
2. Adavantage of using Heuristics and Oracles.
3. Simple tools like testersdesk.com and some perl clip scripts.
4. What is Session Based Test Management (SBTM) and how to implement SBTM.
The workshop on the whole was a great place to meet fellow testers from / in chennai and share our thoughts about testing. I felt many such workshops and meetings should happen and more knowledge should be shared about testing in Chennai. (I am jealous about testers in Bangalore). This workshop was not the kinds that speaks about regular testing, but something different wherein you could learn the other aspects of testing which is not seen in testers everyday life. Also learnt that the more we discuss the more you can extract from a person.

April 19, 2010 Posted by | Uncategorized | , | 9 Comments

Bandwidth Throttling for testing

Not every one has the luxury of using  high bandwidth connections, you can witness and see the difference in the internet connection speed in your office and the one at home. These variations which we see at home, office etc depends on the bandwidth we have or can afford to have.

To know more about bandwidth throttling click here.

Its important to take care that our application performs reasonably good in different bandwidth, To check this we cannot afford time and money to go to places where we can  test for different bandwidth, The solution for this is the reason for this post.

I am not going to explain how these add-on / tools work but will be just sharing these add-on / tools in this post.

I had put forward a query in twitter if anyone knows any tools or ideas to test the application performance under different bandwidth,

Rob Lambert shared a proxy tool which u can find it here. So this led me to ask people if there are any other tools which they use so that i can evaluate the tool which suits my purpose and use it,  I did a quick google and stumbled upon a firefox add-on which can be found here.

Both the tool seems to be cool but the FF add-on was easier to install and run my application for different bandwidth 🙂

If you have any idea’s  or tools or anything informative to share regarding bandwidth throttling please do share .

Thanks

~Bharath

December 13, 2009 Posted by | Uncategorized | Leave a comment

Observation, A skill every testers needs

After a short gap CWT had its 6th session where a game was played to test the observational skill of testers. Observation plays a vital role for every tester, a tester has to observe each and every behavior of the application and reports issues if any.

This was the game played in CWT 6. The mission was to get the highest score in 30 min. All the testers felt that the game was really cool and would help all the testers. I managed to find few methods to crack the game and get 250 points.

Methods to crack the game were,

1. Using browser back and front button before submitting and get 10 points.

2. Using browser back and front button after submitting and get more  points for the same question.

3. Using firebug to change the score.

My learnings:

1. I felt my observation skill was OK and have still more to improve on that skill.

2. The patience to observe , remember, answer was not there once I found the way to crack the game.

3. How changing of requirements affected testers who started testing and did not check for any change in requirement in the middle of their testing.

4. Managing people and also scoring points within the time period.

Bharath

https://ticketnumber.wordpress.com

December 13, 2009 Posted by | Uncategorized | 4 Comments

CWT 4 with zettels

Application Tested: https://www.zettels.info/un/ (A Personnel organiser)

Testers: Bharath , Krishnaveni , Pragnya

Mission : Find as many bugs as possible.

Zettels is an interesting personnel organizer application where u can put in short notes, videos, links to your favorite websites and many more. We can also share these to other persons through email and many more. If you want to have a look at the application click here.

Owing to Diwali cwt did not meet for the discussion , but still managed to receive few reports.

My Experience on the report,

1. The application looked small but it had too many functionalities to give to the user which i felt could have been more organised better so that there is no bottleneck to           understand the application fully.

2. Usability is a concern in this application.

3. Navigating within the application had hiccups as i was a bit confused on how i got to one particular page and how i can get back to the page i came from.

4.  This made me think on how to manage complex sites and plan our testing activity. Possibly a post in this regard would be great from my side 🙂

5. You can find the report here.

Thanks

Bharath

https://ticketnumber.wordpress.com

November 1, 2009 Posted by | Uncategorized | 1 Comment