This is a quick review of the book “Lessons Learned in Software Testing” in a different way. I hope you would like it. Check it now.
10 Worst Things a Critic Would Say About Your Software:
It is a typical practice to include the list of known issues with the QA sign off an email.
This helps teams make the right decisions as to:
- Let the end-users know the problem areas
- Plan for training accordingly
- Work on Change Management
- Include these issues in the help files or documentation, so we provide alternatives, etc.
The list includes confirmed defects that were either deferred or not fixed due to time constraints and such.
I came across an interesting concept that is related to this concept recently during the re-read of “Lessons Learned in Software Testing: A Context-Driven Approach- by Cem Kaner, James Bach, Bret Pettichord”.
One of the lessons in this book was: “Lesson 209: A useful release report lists the 10 worst things critics might say.”
The book suggests that when QA is done testing and during sign off it is a good idea to include a list of 10 things that the critics might say about the product. This list could influence whether the product is ready to go live or not.
Further explaining this point, the book says: “…this approach lets you maintain your position as a critic of the software, rather than attempting to provide a fair assessment of the software.”
This felt like such a good idea, totally do-able and extremely useful. I was wondering why I have never done this before.
How is this different from the known issues list we are already providing?
The former contains only the confirmed bugs not fixed yet. Functionality that isn’t working as intended – mostly minor ones. You are confined by the boundaries of ‘what is the software supposed to do’ and ‘what it is not supposed to be’.
Critics have no such limitations.
So, this is where you could get candid and give your honest opinion.
What might this list contain?
- Functionality problems
- Performance issues
- Design suggestions
- Enhancement suggestions
- Clarity and relevance of error messages, etc.
Let’s do this for an application that is a car dealership site of sorts. It is a work in progress. Let’s assume the first release testing is done and is now ready for release.
Also check => More Software Testing Exercises Here
So, here is what my top 10 critic list would be. Also, since you are going to be unfamiliar with the site, I am going to include screenshots (wherever applicable) for an explanation.
What You Will Learn:
10 Worst Software Critics Based on “Lessons Learned in Software Testing
(Note: Click on any image for an enlarged view)
#1) The hero image title capitalization could be better. Right now, it says “realize your dreams”. It looks better as “Realize Your Dreams”
#2) The “BUY CARS” page takes the user to the home page too. We have decided to implement the functionality in the future releases, but for now, it might be better to remove the “Buy cars” menu item altogether.
Why give the user something that they can’t use?
#3) Sending a message to a dealer is a good idea. However, cars salesmen are famous (or infamous) for not letting the customer leave without buying the car. So, a chat option might be more on point.
#4) The “Write Your Message Here” text is accepted as the default one and when the message is submitted, it sends the body of the message as “Write Your Message Here”. The default should be empty.
#5) Nowhere on the site, there is a sale policy mentioned. It might be a good idea to include that too.
#6) The Favicon can be more effective. Maybe include a mini-car there?
#7) “CONTACT US” page is going to have a form that the user can fill in order to have their queries resolved. Until that happens, an email or a phone number or a physical office address as the static text has to be displayed.
#8) The user interface is good but a bigger and higher resolution car image can be more impactful.
#9) It is hard to navigate to the home page from the admin module. It does not have a “Home” link.
#10) The “VIEW INVENTORY” term for the site sounds too industrial. To make it more readable we must try “FIND YOUR CAR” or something along those lines.
The list is not exhaustive and not always a constant. Different team members can have different insights. There can also be more than 10 items on it. Pick the ones that seem most relevant.
Also, note that only a few of the items are functional problems.
I had fun doing this because who does not like pointing out problems. Right? :)
Exercise for you:
For beginners and experienced professionals, this would be a wonderful practice so I urge you to try ANY site/mobile app/windows system and critique it. If willing to share, share the URL of the application and your list in the comments below. We would love to compare notes with one another.
Recommended read =>“10 Lessons Learned in 10 years of Software Testing career”
A quick book review- “Lessons Learned in Software Testing”:
Finally, I can’t finish this post without pointing out a few things about “Lessons Learned in Software Testing”.
This is my second time reading it. The first time, I took everything at face value. But now, it was so wonderful to test my knowledge. If you haven’t read it already, I highly recommend trying it.
What will you find in this book?
There are 293 points in the book. The topics range from what it means to be a tester, testing techniques, automation, bug advocacy, test documentation, context-driven-testing, people management, etc. If this happens to be your first book and introduction into testing, you are in good hands.
What will you NOT find in this book?
This is not a practical guide to anything. So, if you are looking for practical concepts on how to write test cases or how to calculate function points, this book is not what you should be reading.
Here are a few excerpts from the book that grabbed my attention and might pique your interest:
- If you expect to receive requirements on a sheaf of parchment, stamped with the seal of universal truth, find another line of work.
- When you perform a test by hand, you bring to bear the entire range of human capabilities. You can improvise new tests or notice things that you did not or could not have anticipated. Test automation is a faint, tinny echo of that rich intellectual process. That’s why it’s nonsensical to talk about automated tests as if they were automated human testing.
- Not all problems will be fixed. Don’t insist that every bug should be fixed. Pick your battles!
- If you declare there shall be no heroes in your company, you won’t get any (Talking about people management)
- Be a volunteer, not a victim. (This can be easily taken out of context. It is a point that reminds us to prioritize your obligations and plan accordingly)
- A template is no substitute for skill.
Overall, it was a very satisfying read.
Over to you
Hope this quick review of “Lessons Learned in Software Testing: A Context-Driven Approach” book was helpful to you.
What software Testing books did you find most useful? Also, if there are any books you would like reviewed here, do let us know!
About the author: These 10 critics and book review compiled by Swati S. – STH team member.
Happy critiquing! We will be thrilled to read your findings.
7 thoughts on “Review of the Book ‘Lessons Learned in Software Testing’”
Nice article Swati S. Very very useful for the both entry level and experienced professionals. I will definitely gonna buy and recommend this book to all my testing colleagues and friends those who wants to starts their career in testing. Thank you so much for sharing this article with testing family and
Thanks to STH team. LESSON LEARNED IN SOFTWARE TESITNG
I see of the points you mentioned are very important. I have doubt.
are you sure you recommend this practice, “Wait for sign off mail to report/mention such issues”.
What we do is – We open/log such issues in our bug tracking tool as “Suggestion by team”. Most of this are to be solved reasonably. So our PM do prioritize them and we get them fix before release.
All I am trying to say is the approach you mentioned it “issue detection” and what we are working is “issue prevention”
what say ??
We can easily convert “What critic would say” into “Improvements” and log them into Jira or any other issue tracking system. If we give freedom to every team member to suggest improvements then we don’t require such list instead we can assign those improvements for client feedback :) at the time of QA Sign off.
Agree with Sachin Sharma :)
@Kiran:Thank you! Do share your thoughts on the book, when you read it. :)
@Sachin Sharma, @Darshan Satish : Thank you for sharing your thoughts. You are right. You don’t have to wait until the sign off. But we all know how teams are swamped with making things work during the test cycle and hardly have breathing room to consider ‘good to have’ suggestions or improvements. Going overboard on reporting these during the test cycle could bring out negativity and resistance to accepting these as valid defects. When the release is set to go, you can say what can be improved to make it better and your gut feel about the system. I will leave it to you when and where(JIRA, etc.) you want to address these. This is a mere suggestion that testing does not end at the test cycle and the test teams should play the end user’s advocate and say what might eventually be received as user feedback. I hope this helps!
I agree with @Darshan Satish, we can convert “What critic would say” into “Improvements”…