Tuesday, December 03, 2013 03:54 AM
Please click on the above link and extend your support.
Tuesday, November 19, 2013 18:49 PM
I and my friend Sanket Gagneja were involved in a paired testing session. We had two mobile devices with us. One of the devices had the app which acted as the oracle and the other had the test app.
I was keen on using the test app as I was new to this app. Sanket was testing this app since few days.
He was the note taker and would answer my questions.
I tapped on an icon, typed "test3" and tapped another icon. There appeared a popup with some text. I was reading in my mind and told to Sanket this line "Your development team has really done a good job" and then THE APP CRASHED.
We both looked at each other for a second and emailed the logs. I tried to replicate the issue and once the popup appeared, the app did NOT crash. I immediately pressed another button.
Sanket took over the device and tried the steps. Then, Sanket did something which made me very happy. He not only repeated the steps but went ahead and told the line "Your development team has really done a good job" and THE APP CRASHED.
He was smart enough to not get diverted and actually remembered the exact sentence and repeated it. It is not about remembering the exact sentence. It is more about being aware of what happened, what's happening and is this what is called as "Situational Awareness"?
PS: The app seemed to crash after 10 seconds of inactivity once the popup appeared and we took 10 secs on average to say that sentence.
Sunday, November 17, 2013 13:56 PM
If the next test is influenced by learning from the previous test, you are applying exploratory testing approach.
Good testing requires skill and good testers work on their skills.
Work on your skills. Do not just restrict to testing related skills. Learn from other disciplines. Spend time practicing the skills. Only those who work on the skills will survive.
Experience matters a lot. Try to experience as many different contexts as possible. The varied experiences and the experience in a particular context helps you think of different and useful test ideas which would help you in testing.
What is the use of any product if it does not solve customers' problems? Do you understand your customers and the context well enough to design your test strategy? I do understand that customers is one of the factors in context.
My first question to the product owners and the programmers in my company: What is the biggest risk you feel with this feature? What are you worried about the most? The answers help me a lot in understanding the product and the project a bit more in detail.
Exploration:This is related to the "Experience" point. In any aspect of the project, pay additional attention to exploration path. Do not restrict it to just testing. Explore in the true sense - to investigate.
Finally, a tester with good testing skills and who is skilled at Exploratory testing will be able to help any project and not just Agile testing projects. This tweet sums up the essence of my talk:
Wednesday, October 30, 2013 08:44 AM
Monday, October 28, 2013 21:34 PM
|Day1: Agile Testing Days|
“Compressing Test Time with Exploratory Methods: A Practicum”
Wednesday, October 23, 2013 05:38 AM
And I did realize that many testers are still hesitant to pay 800 INR on testing books.
So, here is the deal:
Feel free to download the books for free.
Book 1: What If: A collection of tips from a software tester
Book 2: What If: 50+ tips to win testing contests
Book 3: What If: 50+ tips to boost your productivity
Book 4: What If: 50+ tips to improve tester-programmer relationship
Book 5: Mobile Testing: Ready Reckoner
Book 6: UI and UX Testing: Ready Reckoner
I don't want to upload a zip file and let it lie unzipped for months together.
I am aware of the risk that some of you might download and not read it any time as it is free.
This post is for those who wished to buy but cannot afford it at this moment.
Friday, July 26, 2013 02:50 AM
This time, I am conducting this course in collaboration with STeP-IN Forum and the target audience is testers with experience between 0 - 3 years.
Date: August 1st to August 30th (excluding weekends)
Time: 06.00 am to 07.30 am IST
Link to Register for the course: http://stepinforum.org/software-testing-training
As highlighted in the mind map, this training will focus on the following topics:
Basics of Software Testing
We will start with understanding the basic terms like bug - issue - quality - defect. We will definitely NOT go through V-Model, Waterfall and many other such terms which is slowly losing out its importance in today's testing world.
This session will focus on how to generate test ideas, learn from different sources to test any product. We will also know that software testing is not only about testing Functionality.
There is no fun without bugs. So, how do we find them? How is bug investigation different from bug hunting? How to find Sev 1 bugs?
We will definitely be using many tools in our sessions. We will also focus on how to scout for resources and tools in particular.
Once a tester completes the test execution, (s)he should be able to provide a professional test report. We will create different reports and get feedback from the group.
Does your learning stop after a course or workshop? How can one learn about software testing every day? We will go through few important areas for self-learning.
Link to Register for the course: http://stepinforum.org/software-testing-training
Tuesday, July 16, 2013 18:16 PM
Sunday, July 07, 2013 04:10 AM
After STeP-IN, its time for World Conference on Next Generation Testing by Unicom.
I am excited to be part of this conference for multiple reasons.
This is the first time, I am conducting a paid workshop on Exploratory Testing. Details about the workshop are here (Click on the Agenda tab). This is a one-day workshop and you can register here. The speaker list is impressive. I have known many of the speakers for quite a few years now.
I take this opportunity to let you know of three reasons why one should attend this conference:
Reason 1: The Experience & Knowledge
If you have never attended any conference till date and you are working in software testing industry, I would say that its too late. You need to experience the conference atmosphere. Better late than never. Get started. Once you attend, you will know about different contexts other than the one at your office. You would also know that you can present in next conference too.
Reason 2: Build your Network
It is good to know that others share your passion or have interests just like your team. The problems faced by your team are already solved by some other teams. You may never know whom your company might hire in next three months or which domain interests you after six months. The bigger your network, higher your chances.
Reason 3: Good Investment
When I started my career in software testing, I paid one-fourth of my salary for a half day workshop. Friends called me crazy but the investment paid off big time. My perspective on software testing changed. And today, I have reached a state where I would conduct a paid workshop. Do not wait for your employer to pay for your learning. Invest in self-learning and reap the benefits soon.
I will be available at Le Méridien from 10th to 12th July. See you there.
Sunday, June 09, 2013 08:55 AM
Over the last two years, I have practiced and used mind maps to collect all sorts of information.
Starting from test ideas to book draft to bug investigation, I have gained a lot by using mind maps. I have also conducted workshops at Hyderabad and Chennai on usage of mind maps in testing. It was well-received. So when STeP-IN agreed to my topic of mind maps, I was happy. I see this as an opportunity to help more testers realize the power of mind maps and save a lot of valuable testing time.
Do attend STeP-IN Summit 2013?
Thursday, May 30, 2013 19:49 PM
Book 1: Mobile Testing: Ready Reckoner
So, in the event held few days ago, I and my friend Sundaresan Krishnaswami wrote a book on Mobile Testing. We admire Jonathan Kohl's book 'Tap into Mobile Applications' a lot and have learnt a lot from the book. We needed a ready reckoner - a very short book and we created it based on our readings, testing experiences, competition experiences and feedback from other testers.
Each page is designed in such a way that an idea is explained with the help of a screenshot. We have also added the learning and resources link if necessary. As a tester or a mobile enthusiast, you can open any page and apply the idea immediately.
You can print the entire book and have it as a pocket calendar. The book size fits the pocket.
Saturday, April 13, 2013 17:50 PM
"What is smoke and sanity testing and how is it connected with high level test cases?"I asked why he wanted to know the answer and pasted the link to blog post by Michael Bolton:
I told them that it is much more important to practice testing and improve one's testing skills than know answers to such questions. When I mentioned about BBST, I was asked if BBST meant Behavior Based Software Testing. I was disappointed and emailed the tester my first book - 'What If... A collection of tips on software testing'. To my surprise, the tester had already bought this book. I was even more disappointed.
The next day, I received this email from the tester:
Now I am feeling like this book is the best gift given by anyone and once more thing initially i was using it like quick recap but today i feel that it is more like an encyclopedia of testing basics.
Sunday, March 24, 2013 17:22 PM
In one such testing session, I found a bug where the button was tapped even though I did not tap the button. On further investigation, I realized that the focus of the button was much more than the button area. Let me highlight the issue with the help of the following image.
On the left image, we have a problem. The button's perimeter is displayed by red color.
But when the user taps or clicks anywhere within the green rectangle, the button is still clicked.
On the right image, the focus of the button is limited to the area highlighted by red color. On tapping or clicking outside the red area, the button is not activated.
How do we usually test such buttons?
- Clicking on the button
- Changing the state of the button - enabled/disabled
- Test the default state of the button
- Combining the button action with other actions
Just to confirm: This is different from "Boundary Testing technique".
Sunday, February 10, 2013 18:35 PM
Here is the mindmap and the mnemonic. Thanks to Michael Bolton. http://www.developsense.com/blog/2010/11/context-free-questions-for-testing/
PCM - TRP - DOT - TED - FIAT
Wednesday, February 06, 2013 05:28 AM
Anurag & myself discussed about various testing challenges including
- building awareness about testing
- continuous learning
- relationship with programmers especially when they are not in the same time zone
- counting bugs
|Junglee Search Bar|
- Why did I record the session
- How to use Comparable Products heuristic
- What was the test idea behind using script tag attack
- Special cases discovered in the session
- Persistent XSS Attack
- Http codes
- Difference between SupportDetails.com and .net
|Plan for a new project|
- Xenu link checker
- Firefox addon - Extended Status bar
- Article on Cookies
Wednesday, January 30, 2013 18:26 PM
Monday, January 28, 2013 18:22 PM
Sunday, January 20, 2013 16:42 PM
This post is to convey two points:
I am sorry for the unintended break
I got a new job, got busy and can give many more excuses but the truth is I did not facilitate the sessions. I am sorry for it and I promise to dedicate time for Weekend Testing once again.
Weekend Testing is back and is here to stay
This Sunday onwards, we will have sessions regularly - hopefully, every weekend.
The site contents have been simplified
- Removed unused content/options
- Removed registration link - I don't see a need for testers to register. Also, the % of spam users seems to be greater than testers.
- Just the required content is present.
Saturday, January 05, 2013 17:53 PM
Saturday, December 29, 2012 18:09 PM
Two more books in What If... series.
When I wrote my first book, I did not realize that I could write three more. The first book took more than three months for me to complete. The response by the readers and testing community gave me the confidence to complete each of the next three books in three days each. I have testers emails and chat messages thanking me for the book. It was well received. Thanks to the readers, I plan to write more and not restrict to just two books per year.
If you have not bought my books yet, here is the post with the details:
I joined Fiberlink
Everyone keeps changing companies. I did after five years and six months of working at efi. There was no formal interview conducted. They liked my work, called for a chat and offered me the job. I was very impressed when I saw that they were using cheatsheet by Elisabeth Hendrickson. I could sense the passion they had towards exploratory testing and they were talking about exploratory testing. I knew that it would be fun working with them as they seemed to be passionate about software testing.
Its been eleven months and I am still enjoying. I got the Best New Joinee award and every day teaches me something cool.
Online training on software testing through Skype
I started training over Skype and there was a good response. I met many testers online. And some of them are really good. After completing four batches, I think that I should continue this exercise in 2013 as well. I do train testers on a 1-1 basis. If you are interested, ping me.
Workshop on software testing
Once I conducted the online training, I realized that I can do it onsite too. Thanks to Chennai Bug debug and Hyderabad testers meet, I conducted a one day workshop at Chennai & Hyderabad. Testers liked the presentation style and the content. I learnt a lot about conducting courses.
I went to Rapid Testing Intensive event at Orcas Island for a week. The most hectic course I have attended after BBST and the best place I have visited till now. A superb combo. I can safely say that I have restarted my journey as a software tester after attending this course.
With the five points listed above, I end the year 2012 on a very happy note.
I look forward to 2013.
I did not have many expectations when I started 2012. Its the same with 2013. I am prepared. Let's see what's in store!
Tuesday, December 25, 2012 18:30 PM
Book 1: What If... A question every software tester must ask.
When I logged my first bug, I thought – ‘What if’ this bug was found after release? Years passed, many products were released, and I gained a lot of varied experiences. I made a few embarrassing mistakes too. There were few instances where I wished that someone had warned me beforehand. So, I started preparing a book of tips targeted at software testers. Special care has been taken to keep each of the 22 chapters short and to the point. Emphasis is on ready-to-use tips which would give you instant results.
Book 4: What If... 50+ tips to improve tester-programmer relationship
This book brings into picture a very important person - the programmer & the programming team. Each one of us might have the experience of working with at least one tough programmer. Some programmers are very friendly and help us with finding bugs. Some of them are very strict with their deliverables and do not respond to any queries outside office hours. Some hardly talk to you unless you ask them a question. There are different types of programmers and bring in variety to our testing challenges. As I write this book, I have completed over six years of software testing and interacting with multiple programmers across different projects within and outside the company. With a rich experience of working with tough programmers, I write this book to help you.
My special thanks to my family members (for having a gap between the birthdays), my friends for accepting me as I am, my friends on twitter, facebook who keep encouraging my work, the programmers who keep challenging me, those who bought my first three books, those who provided me feedback and those who continue to believe in me :)
And of course, my love and thanks to my father who continues to encourage me in everything I do.
How to buy the books:
If you want to buy all the four books, please transfer INR 525 to my bank account or USD 13 by Paypal.
Account No: 00531610015960
Bank: HDFC Bank
IFSC Code: HDFC0000053
Paypal email: email@example.com
If you want to buy just the fourth book, here is the link: http://imojo.in/UZBvi5
Wednesday, December 12, 2012 06:45 AM
Wednesday, December 05, 2012 16:08 PM
Friday, November 30, 2012 18:03 PM
I wanted to go through every bug logged and at the same time understand the application quickly. I started with few bugs and then an idea struck me. Why not map the bugs and categorize the features too as parent nodes?
This is what I got after 25 mins:
|Mindmap of Bugs|
This way, I went through every bug and still made a high level model of the entire application.
I liked it and after three hours of testing, I got the 7th position with 100% valid bugs. I logged 6 bugs.
Maybe, there is a better approach but I liked the approach of mapping out the bugs before testing. What do you think? Do you have a better way?
Friday, November 23, 2012 02:29 AM
As soon as I got to know about the book https://leanpub.com/testmobileapps by Jonathan Kohl, I wanted to read it. The request was approved and I got a chance to read the book on the same day.
As seen on the site, the book covers a wide range of topics necessary to know about mobile app testing.
What did I learn from this book:
Reading the book was a very good experience. Every page had something new. I liked the initial chapters a lot compared to the strategy, planning chapters. I wanted to read this book on my mobile phone - landscape mode using QuickOffice Reader. This experience helped me find some bugs in QuickOffice Reader application and I could also experience using a mobile app.
Examples of different types of bugs
I like the books where the authors don't just mention what to do but also highlight their experience when they followed their own advice. Jonathan Kohl does a great job in highlighting his experiences in testing different types of mobile apps and what kid of bugs he found. Some of his bug stories are like the detective puzzles and teach you a lot.
What's inside a mobile and how it can affect tests
To be honest, I knew very little about the mobile hardware before starting this book compared to now when I am writing this blog post. You regularly move your mobile but are you aware of which sensors are affected? Do you have any idea of how your test results are indirectly and to some extent, directly affected by the mobile hardware? This book has a dedicated chapter and is a good starter for someone like me.
Though there are many tours mentioned in this book, I like the Gesture tour. Pinch/Tap/Flick/Swipe/Press - Which gesture do you like? I tried few of the gestures and found bugs specific to them. There are many different types of tours mentioned in this book. Ok, he not only mentions them but also explains as to how to conduct each tour.
Testing Mnemonics for Mobiles
Jonathan Kohl - creator of I SLICED UP FUN mnemonic also explains about few other mnemonics in this book. As a tester, its good to know such mnemonics so that you can apply them as and when required instead of thinking of new tests every time.
Dealing with Intermittent bugs
This topic is not new to many testers. James Bach talks about such bugs here - www.satisfice.com/blog/archives/34 BBST course - Bug Advocacy section too highlights tips to tackle such bugs. www.testingeducation.org/BBST Jonathan Kohl talks about intermittent bugs found during testing mobile apps. Small distractions, movements, network changes, orientation differences - how can they affect the bugs - the topic covers them all.
The book is worth the cost. Hope Jonathan writes more such books and continue to help the testing community. Thanks Jonathan Kohl.