Tuesday, April 14, 2015 14:31 PM
When Nazreen called me and explained me about this situation, she did mention about an interpreter too who could help me communicate with the two boys. I gave them few exercises over email and I could not assess the skills to my satisfaction. I wanted to spend time with them to understand the context better. V-Shesh decided to fly me there and get me back to Bangalore, the same day.
As soon as I reached NISH, the two boys were ready and raring to start learning? No, they thought that I had come to interview them. Once I clarified with the interpreter that I am only a software tester and have no say in hiring any individual. I did not want to give them a plan without understanding their context. I had never interacted with any software tester who was deaf.
I assumed that they would be able to lip-read and understand. I was wrong. When my colleagues themselves find it a bit hard to follow me sometimes, I shouldn't expect much in the first interaction itself.
I asked for few sheets of paper and we communicated by writing on that paper.
Challenge 1: Assess the current situation
When I gave Appu to write about what he knew about software testing, he started writing about the definition, requirements, validation, verification and so on. I realized that the day was going to give me new challenges.
Kannan responded to my questions in his own way. His task was to test Amazon.com - Search feature and give me list of bugs. He showed me the first bug report with a smile [Remember that there is no sound involved here. I am not talking and they are communicating using their fingers] When I asked Kannan about the oracle behind the bug (I used simple terms - Why is this a bug), he pointed me to the invalid test data. I
I knew that this would take a lot of time and I have only 3 hours left before my departure to Bangalore. Meanwhile, I had asked Appu to read about Context-Free Questions blogspot and Kannan to refer the 400 Common Software Errors.
I then wrote a letter to Appu and Kannan and requested the interpreter to convey the message via sign language.
A letter to Appu and Kannan
Congratulations on giving your best to learn software testing. I am impressed by your attitude and your willingness to learn about software testing.
You are better than many software testers available in the world, working in different companies. They are already in the company, we are yet to get into one.
I have a plan on how you can get into the company of your choice. Yes, your choice.
When will any company want to hire you?
- You are good. You are better than their test team.
- You can test any software and have experience testing different types of software
Right now, you know to find bugs but you lack practice to explain why you think it is a bug.
If you are ready, I have a plan for you:
It is a 10-day plan. With this plan you can learn to test any software.
1. Understand the requirements
- Context Free Questions
- Mary had a little lamb heuristic
- Understand the purpose of testing
2. Write test cases / Have checklist ready
- Write test cases
- Different Quality Criteria
3. Find bugs
- List of common bugs
- Techniques to find bugs and justify why a bug is a bug
- Tools to help you find bugs
4. Prepare test report
- Details of what you tested
- Details of what is pending
- Details of status of project and product
If you learn how to test mobile apps, websites, desktop applications, you will have higher chances of getting into a company.
I will demo you how to test website, desktop, mobile app.
Then you can also demo it to me with another example.
Then we will have online sessions.
Challenge 2: No Internet
They were ready and I asked for a room with whiteboard and few markers. As soon we moved there, we realized that there was no internet. Well, what is the fun without challenges?
We continued without internet and this is the outcome of the discussion over the whiteboard.
Challenge 3: Limited Time
And then I received call from the cab driver to drop me to airport. I realized that I had spent close to 5 hours explaining testing without opening my mouth!!!
I could see the smiles on Appu and Kannan's face. You know what was the most satisfying moment in this whole experience?
Communication - Straight from the heart
When Kannan went to the whiteboard and wrote - 'How do you know Sign language?'
I had tears in my eyes and wrote - I do not know.
I conveyed that I know acting and he nodded. I was smiling inside...
What do you think are the next steps?
I will coach them and get them job-ready in a month or two. I do not know(as of now) the time frame yet. They will work on their skills and get ready for job.
What can you do?
Spread this post, spread the news about them and maybe help them get trained.
My email id: firstname.lastname@example.org
Monday, January 19, 2015 12:24 PM
Thursday, December 04, 2014 04:49 AM
Add some travelling and festivals in between and the challenges multiply.
Thanks to all the participants, the instructors, my course sponsor Ilari Henrik Aegerter and my family members, I could complete the course on time.
Friday, September 05, 2014 01:35 AM
It is going to be a long post highlighting few key points/myths and what I think about them.
Feel free to comment and we can discuss. Ok, let's start.
Case 1: Testing process
You are supposed to test a feature. You receive a requirement document and there is a formal review process. You write test cases based on your understanding of the feature. Add a layer of review process. Start
You are suppose to test a feature. You figure out who is the decision maker, the stakeholders involved and try to understand your role. You seek help, remove traps to get access to the product, interact with the programmers and prepare a light-weight document (checklist/mindmap or on a simple sheet of paper ) which acts as a reference. Based on your interactions with people and products, you update your document. You test the product, file bugs, ask questions, seek help/tips from experts and inform the stakeholders about the status of the product and project.
I will let you pick the scenario you like.
If you are more familiar or in favor of Scenario 1, we will have lots to discuss.
Case 2: Manual Testing vs Automation Testing
Have you heard of the word 'Sapience'? Do you use just your hands while testing? Do you think? What happens in your brain when you test? Think for a minute. Yes, THINK.
I feel that the very notion of classifying testing as manual vs automated is wrong. Michael and James have come up with an excellent blog post here highlighting the difference between testing and checking.
Here is the diagram from their post.
Also, check out this blog post by Michael - http://www.developsense.com/blog/2013/02/manual-and-automated-testing/
These two posts talk about Testing and Checking:
What is testing then?
Before reading more on what testing is, do check out the slides from BBST Foundations which describe what a computer program is. The same folks who would define a computer program as a set of instructions would define testing as a process to find bugs or assure quality of the product and testers as the gatekeepers of quality.
Check out an excellent video on the talk between devil and angel of software testing:
Testing is an intellectual activity. If you can think well, you can test well. Every test is a question to the product, sometimes to the project stakeholder. Check out the lessons #16 and #19
Learning new tools, writing better user stories, automating tasks and dreaming of days when testing would be fully automated!!!
Pick any resume and check the Skills section: 7 out of 10 would mention some or the other tool names.
Quick Learning is a skill. Tool is a tool. A fool with a tool is still a fool (maybe, a dangerous fool).
300 common software errors
Saturday, July 26, 2014 08:16 AM
Before I begin highlighting our team's experience, I want to thank the lead organizers - Matt Heusser and Maik Nogens and all the volunteer judges, the sponsors and everyone who helped conduct this BIG contest at the highest level. Check out the website for more details: Software Testing World Cup website
The logo is quite good too :)
Saturday, March 15, 2014 15:17 PM
There have been instances in my previous and the current organization where I am called upon to help a project which is going nowhere. Most of the times, they face one of the situations:
- Important bugs being identified late
- Testers on unplanned leave
- Unstable product or need for better coverage
- Inexperienced project team
- Important project
|My Project Preparation|
Monday, March 10, 2014 07:39 AM
If you answered yes to any of the two questions, I have one more question for you :)
What percentage of office time do you actually test (interact with the software)?The answer to 'Testing includes...' might differ from one person to another. I don't want to get into that discussion right now. I am more concerned when people spend very little time interacting with the product and complain of bugs being found by the customer. Consider the following three scenarios:
A feature has been revamped and will be released to market soon. A tester who has never worked on the feature is called to test the revamp. The tester could:
- Understand the existing feature
- Understand the revamp
- Analyze the XYZ specification
- Write test cases
- Test the feature and file bugs
- Test the system
- Attending meetings
- Updating KnowledgeBase pages
- Plan for next release
- Taking interviews
- Document the learning
- Understand the mission quickly
- Highlight the traps and risks
- Test the feature, system
- Use information from different sources as a heuristic
- Get help from those who can help her
Thursday, January 09, 2014 09:49 AM
Check out the following tips. Hope they are of use to you - especially if this is your first time.
Abstract / Description
- Let it be as simple and crisp as possible.
- Do not copy paste or explain your company or context or a technology in detail unless it is a new idea. On some of the abstracts, I have seen a lot of details about some well known technology which could have been googled.
- Please get it reviewed by someone who has already presented a paper or presented in a conference.
This is one section which the audience is more interested in, specifically when they need to choose between sessions. Some not-so-good examples of Key Takeaways:
- XYZ Technology or Some terms in ABC Process
- X% improvement in some method
When submitting a paper, please test it.
- Will you as a reviewer, like it?
- Is it really necessary to give you a speaking slot?
- Is it something which needs you or can be found on Internet?
These are three questions which when answered might give you a clear picture of whether your paper is good for a conference submission.
Tuesday, December 31, 2013 13:34 PM
Five more lines before I end this blog post.
Thanks for everything that happened in 2013.
Thanks for every experience, I learned from and specially the ones, I couldn't learn from.
Thanks for the good health and wisdom to choose the right words.
Hope to live one more year of experiences, learning, caring and contentment.
Have the courage to give wings to your dreams before its too late.
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