Entries from 2009
Guidelines on writing Defect Description
Defect can be expressed as “Result followed by the action”. That means, the unexpected behavior occurring when a particular action takes place can be given as defect description. 1. Be specific. State the expected behavior which did not occur – such as after pop-up did not appear and the behavior which occurred instead. 2. Use Read More...
Guidelines on deciding the Severity of Defect
Indicate the impact each defect has on testing efforts or users and administrators of the application under test. This information is used by developers and management as the basis for assigning priority of work on defects. A sample guideline for assignment of Priority Levels during the product test phase includes: 1. Critical / Show Stopper — Read More...
What is a bug?
Bug can be defined as the abnormal behavior of the software. No software exists without a bug. The elimination of bugs from the software depends upon the efficiency oftesting done on the software. A bug is a specific concern about the quality of the Application under Test (AUT). Read More...
Root file system
Describe about the root file system. The root file system has to be present for the system to execute /bin, /dev, and /etc are always kept on the root system because when the system starts only files in the root system are accessible and some files such as /bin/sh are needed to run at all. Read More...