A Formal Definition of Software Bug
by Nataliia Vasylyna | March 29, 2016 10:13 am
Everyone, who is interested in software testing or has heard something about it, understands what a bug is. But not all are able to explain the exact conditions of errors occurring.
The term ‘bug’ is closely connected with product specification. It may be also called spec. The specification[1] is the detailed description of every aspect of the project. It concerns the product functionality, capacity, interface, design, etc. The spec determines what functions the product should perform and what it should not.
When Do Bugs Occur?
- If the product does not perform some action which is specified by the spec.
- If the product does the action which should not be carried according to the spec.
- If the product operates in the way which is not mentioned in the spec.
- If the product does not execute the action which is not specified in the spec but it should be.
- If s tester is sure that the product is complicated to use, it is even difficult to grasp the general idea of its functioning and the system is too slow.
As a specification is written by people, then some mismatches and misinterpretations may occur. This kind of errors is called a specification bug. It is a nightmare for the development team and the specialists from software testing company.
Learn more from QATestLab
Related Posts:
- specification: https://qatestlab.com/resources/knowledge-center/sample-deliverables/
- How a Software Bug Can be Called?: https://blog.qatestlab.com/2016/03/28/possible-bug-names/
- Software Bugs. Definition and Meaning: https://blog.qatestlab.com/2011/08/02/software-bugs-definition-and-meaning/
- What is the price of a software bug?: https://blog.qatestlab.com/2016/03/31/what-tester-does/
Source URL: https://blog.qatestlab.com/2016/03/29/software-bug-definition/