Review of the Book ‘Lessons Learned in Software Testing’

This is a unique perspective on the evaluation of the book ‘Experiences from Software Testing’. I trust you’ll find it enjoyable. Have a look right away.

10 Possible Detriments Software Critics Could Mention:

It’s standard protocol to include with the QA certification email a roster of already identified problems.

This aids teams in making knowledgeable determinations concerning:

• Advising end consumers of areas of concern
• Organizing applicable training
• Undertaking Change Management
• Integrating these issues into the aid files or manuals to offer substitutes, and so on.

The inventory identifies proven bugs which were either deferred or unresolved because of time limitations, and so forth.

[image credit]

Lately, while examining the book “Experiences from Software Testing: A Context-Driven Approach – by Cem Kaner, James Bach, Bret Pettichord”, an intriguing idea related to the subject piqued my interest.

The book mentioned this interesting lesson: “Lesson 209: An efficient release report incorporates the 10 most critical comments critics could argue.”

The book recommends that during the sign-off phase, when the QA crew has completed the testing, it’s prudent to include a roster of 10 comments critics might have regarding the product. This roster could potentially impact the verdict whether the product is ready to hit the market or not.

To expand on this, the book notes, “…this method enables you to sustain your role as the software critic rather than endeavoring to deliver an unbiased appraisal of the software.”

I found this concept not only genuinely intriguing but also entirely doable and hugely advantageous. It’s surprising I hadn’t considered it previously.

How is this different from the known issues list we already provide?

The latter catalog only includes confirmed unresolved bugs. These are functionality issues not working as expected, primarily minor ones. The list is bound by the limits of ‘what the software is supposed to do’ and ‘what it’s not supposed to do’.

Critics, conversely, are not bound by such restrictions.

Therefore, this is the juncture where you can provide straightforward feedback and express your honest opinion.

What could be included in this list?

• Functionality issues
• Performance worries
• Design suggestions
• Enhancement proposals
• User interface/user experience
• Clarity and pertinence of error notifications, etc.

Sample practical exercise:

Let’s apply this to an application designed as a car sales site. It’s currently a work in progress. Assume the initial testing for the first release has been finalized and is now set for launch.

Also, look into => Additional Software Testing Drill Here

So, below are the top 10 complaints about the software. Because you may not be acquainted with the site, I’ll supply screenshots (where applicable) to clarify.

10 Primary Criticisms Identified from ‘Experiences from Software Testing’

(Reminder: Click on any photo to enlarge)

#1) The caption capitalization in the primary image could be better. Currently, it reads “realize your dreams”. It would look more professional as “Realize Your Dreams”.

#2) The “BUY CARS” page also redirects the user to the homepage. Even though we intend to activate the functionality in future rollouts, it might be better to remove the “Buy cars” menu feature for now.

Why present the user with something they can’t use?

#3) While dispatching a message to a dealer seems like a solid proposition, contemplating the addition of a chat function might be beneficial. Car sellers are famous for not letting buyers leave without closing a sale. A chat function could be more suitable.

#4) The default text for the “Write Your Message Here” option is accepted as the real message. When submitting the message, it sends the body of the message as “Write Your Message Here”. The default should be blank.

#5) The website doesn’t mention the sale policy anywhere. Including this information might be useful.

#6) The Favicon could make a stronger impression. Perhaps incorporating a small vehicle icon would be more effective.

#7) The “CONTACT US” page might include a form for users to submit their inquiries. Until such functionality is activated, an email address, phone number, or brick-and-mortar location should be displayed as static text.

#8) The user interface is decent, but a bigger, higher-resolution car photo could lend more impact.

#9) It’s laborious to navigate back to the homepage from the admin module. There isn’t a “Home” link accessible.

#10) The phrase “VIEW INVENTORY” feels too industrial for the site. Looking at “FIND YOUR CAR” or an equivalent phrase would make it more user-friendly.

The list is not comprehensive and may not be stable. Distinct team associates could offer various viewpoints. The list can also surpass 10 items. Choose the ones that you find most relevant.

Moreover, take note that only a small number of these points correlate to functional issues.

This exercise was particularly fulfilling to undertake, as who doesn’t enjoy pointing out problems, correct? 🙂

Give it a shot:

For newcomers and seasoned professionals, this would serve as a terrific activity. I recommend you review any website, mobile application, or Windows program and voice your criticisms about it. If you’re comfortable sharing, submit the application’s URL and your inventory in the feedback section below. We’re excited to exchange thoughts!

Suggested reading: =>“10 Lessons Earned in 10 Years of a Career in Software Testing”

Brief Book Evaluation – ‘Experiences Earned in Software Testing’

In closing, I cannot end this text without bringing up a few key points about ‘Experiences Earned in Software Testing’.

I’ve read this book twice. On initially reading it, I took everything at face value. However, the second reading was an excellent chance to put my knowledge to the test. I insist you read it if you’ve not done so yet.

=> Purchase the book here

What can you fetch from this book?

The book discusses 293 points, involving various subjects such as the tester’s role, testing methods, automation, bug advocacy, test documentation, context-driven testing, people oversight, and more. If this is your introductory book on software testing, you’re in a good place.

What will you NOT obtain from this book?

This book doesn’t work as a practical guide for specific undertakings. So if you’re searching for practical concepts on how to draft test scenarios or how to calculate function points, this book might not be what you need.

Here are a few extracts from the book that drew my attention and might draw yours:

• If you anticipate receiving requirements on a grand parchment, marked with the seal of universal truth, it’s perhaps time to ponder another career.
• Executing a test manually brings forth the full spectrum of human capabilities. You can improvise new tests or spot things that you did not or couldn’t predict. Test automation is a feeble imitation of that rich cognitive procedure. Hence, it’s ridiculous to talk about automated tests as if they merged with manual human testing.
• Not all issues will get resolved. Avoid insisting that every bug needs to be fixed. Wisely choose your battles!
• If you declare and enforce a “no heroes” policy in your organization, you won’t have any heroes (referring to people management)
• Act as a volunteer, not a victim. (This proclamation might be misconstrued if taken out of context. It emphasizes the need for prioritizing your tasks and scheduling properly)
• A template is no substitute for proficiency.

On the whole, the read was immensely gratifying.

Over to You

I trust this short evaluation of ‘Experiences Earned in Software Testing: A Context-Driven Approach’ was beneficial for you.

Which software testing book have you found the most valuable? If there are any books you’d like us to evaluate, let us know!

About the author: These 10 criticisms and the book evaluation were collated by Swati S. – a team member of STH.

Enjoy critiquing! We look forward to reviewing your observations.