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).
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.
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 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?
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.
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.
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 .
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.
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.
Application Tested: https://www.zettels.info/un/ (A Personnel organiser)
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.
First of all sorry for the delay in revealing the CWT session 3 report had been on a very tight schedule lately. The Session 3 had a fantastic response and the discussion was really helpful for all the participants in this session. We also had people who had submitted the report but could not attend the session.
Application Tested: http://motismo.com (A project tracking application)
Mission : Hunt for Bugs
As usual the testing part of the mission was informed well in advance and the discussion happened on Sunday 12.00 p/m. The discussion went really interesting that we exceeded the 1 hr schedule.There were a few testers who could not take up the testing mission due to personnel reasons so they had to do a testing and discussion session parallely.
The discussion started with Gunjan as she had to leave early , She highlighted the unavailability of help file on describing few site related terminologies and also she had faced an interesting issue where the screen went blank on registration. Interestingly no one had noticed the captcha missing in the registration page 🙂 and we discussed the importance of having a captcha in the page .
Next it was Krishnaveni who thought the application could have been more user friendly and stressed that the application missed putting in appropriate error message for validations. Krishnaveni finished off her sharing by saying that she could have done better if she had understood the application and planned her testing mission much better.
Karan though could not do his testing before hand but managed to handle both the discussion and the testing parallely. Karan had a doubt on the market value of the application as he felt the application was not very user friendly. But I feel that the market value of an product is not important to an tester its important that what ever product is given to a tester He/She should test it to the best of their ability. Karan had also had some interesting bug , His credentials got expired which he had registered a day before and when he hit the lost password and gave his email id the application popped out an email id not found message. Karan finished of his discussion saying that he had a great time in this discussion and had learnt something new.
Pratiksha also had to manage her testing and discussion time parallely as she came to know about the session just few hours before the session. Pratiksha felt the application looked very rich in its UI so she had the feeling the amount of bugs would be less, But as the famous saying goes, Do not judge the book with its cover proved rite.
Next it was Santhosh , He found that he is capable of finding bugs in a very short time period and generate test ideas for testing without any proper documents which was not the case in his testing missions usually.
Then it was me, You can find my report here.
The overall experience in this discussion was very good and we all discussed about a common bug which we found which is mailers not being sent to users while registering and lack of information of account active period.
1. Managing people in a group chat and keeping the new comers informed about the mission and discussion.
2. Not to judge the application with its rich UI.
3. Implementation of heuristics.
4. Concentrating on one mission and taking care not to divert from the mission completely.
We are back after a successful second session. This time the session happened in a different way as many testers had other appointments.
How did the session happen…
The mission and the application to be tested was given given before hand and the report was asked to be submitted before 04/10/09, 2.00 p.m. This helped many testers who could not come online.
Application Tested : http://www.izzymenu.com/ this is an CSS menu builder.
The application seemed to be an interesting application, But my mind set again made me to search for functional bugs even though i wanted to investigate on the numbers and see the behavior in the application. I had also tested for cross browser compatibility using browser shot and it did have some compatibility issues.
Please find the reports of the participants of the Chennai Weekend Testing Session – 2
You can find my report here.
Krishnaveni’s report Here to view this report open in scribd, login and download the report. The report is not seen clearly as it is in Excel.
Thanks everyone for your active participation for the CWT Session -2.
Finally the surprise news is out !!
I am very happy that Chennai Testers User Group which started as a user group to share testing ideas has shaped into a group where testers participate in testing missions. The user group is joining hands with weekendtesting.com and henceforth shall be called as CHENNAI WEEKEND TESTERS and we will be the chennai chapter for weekendtesting.com
To know more about weekendtesting.com and what do they do click here
Soon Chennai Weekend Testers will have space in weekendtesting.com and all information’s regarding Chennai testing sessions will be available in weekendtesting.com
Expecting great support from all testers joining weekendtesting.com (Chennai)
- Bug-de-bug The Testing Conference
- Software testing conference in India – Bug deBug Chennai
- Experience with usability testing:
- Skilled Exploratory Testing
- Bandwidth Throttling for testing
- Observation, A skill every testers needs
- CWT 4 with zettels
- Hunting Bugs!! CWT Session 3
- Weekend Testing- Chennai Chapter (CWT-2)
- CTUG to CWT!!!
- Finally a logo for Chennai Weekend Testers
- CTUG Session -1