Context For Software Fault, Error And Failure Classification — Tentamen Software Testing Blog


In the previous post, we explained how software fault, error, and failure differ from each other. In that post, we did not provide the context where this classification is useful. Thanks to the community, we got feedback on this post that was valuable in explaining the context where software fault, error, and failure are helpful. We will introduce you to software testing based on the remarkable book, Introduction To Software Testing by Paul Ammann and Jeff Offutt.

How To Accept A Feedback

When you write a blog post and comments are enabled, you need to be prepared to accept feedback. The most useful feedbacks are ones that ask follow up questions or ones that do not agree with your’s blog post message. The problem is that you can not receive that feedback in person, along with visual communication clues of feedback providers. From textual feedback and disagreement with your topic, you could perceive feedback as hostile.

It is essential to dismiss any emotion at that time and concentrate on the feedback message. Remember that person who provided feedback took their time and energy to read your post and to provide feedback. If they did that, their intention is not hostile but to get started a conversation to learn more about blog post topics.

Context For Fault, Failure, And Error

Paul Seaman and John Wilson provided valuable input on my post on software faults, errors, and failures. They both asked for the context where the classification of fault, error, and failure could be useful.

Classification to fault and error could only be useful to developers, not other stakeholders. This post context is that software testing should also be done by developers, but on levels that deal with faults and errors, not failures. For failures, we have testers, technical, and business-oriented. Faults and errors could be determined during the code review of code and unit tests by other developers. The code review is verification software testing that is done by developers. Validation is done by software testers (definitions are also in the blog post).

Originally published at on September 3, 2020.




Founder of Tentamen, software testing agency.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

How to Create an HTML Form That Sends You an Email

Several Technologies to be Used For SaaS Product

Improving Agile for Enterprise Software Development

Which was the first Continuous Integration Tool?

How to Organise a Large Program in Python (Part-2).

How to Optimize Queries in SQL Server

A rev counter in a car

Creating a Web Service API Using Rust Rocket

CURL with client certificate and private key (mutual TLS)

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Karlo Smid

Karlo Smid

Founder of Tentamen, software testing agency.

More from Medium

How Opkey Solves the Most Common Challenges to Automating SAP Testing

Ten Tips

Why do we test at all?

Test Maturity Model