Scribd
Upload
43 views1 page

Istqb Notes

Defects in software occur due to human errors in coding or documentation. If a defect is executed during runtime, it can cause failures in the system. Defects arise from factors like time pressure, complex code, changing technologies, and system interactions. Failures can also stem from environmental conditions that impact hardware. Testing aims to measure software quality by finding defects. Finding fewer defects through testing increases confidence, while finding and fixing defects improves quality. Lessons from past defects on other projects can help processes by preventing reoccurrences and improving future quality. Test planning and control are important to define objectives and compare progress to the plan in order to meet project goals.

Uploaded by

rajkmm36
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
43 views1 page

Istqb Notes

Defects in software occur due to human errors in coding or documentation. If a defect is executed during runtime, it can cause failures in the system. Defects arise from factors like time pressure, complex code, changing technologies, and system interactions. Failures can also stem from environmental conditions that impact hardware. Testing aims to measure software quality by finding defects. Finding fewer defects through testing increases confidence, while finding and fixing defects improves quality. Lessons from past defects on other projects can help processes by preventing reoccurrences and improving future quality. Test planning and control are important to define objectives and compare progress to the plan in order to meet project goals.

Uploaded by

rajkmm36
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 1

Causes of Software Defects

A human being can make an error (mistake), which produces a defect (fault, bug) in the program code, or
in a document. If a defect in code is executed, the system may fail to do what it should do (or do
something it shouldn’t), causing a failure. Defects in software, systems or documents may result in
failures, but not all defects do so.
Defects occur because human beings are fallible and because there is time pressure, complex code,
complexity of infrastructure, changing technologies, and/or many system interactions.
Failures can be caused by environmental conditions as well. For example, radiation, magnetism,
electronic fields, and pollution can cause faults in firmware or influence the execution of software by
changing the hardware conditions.

Testing and Quality


With the help of testing, it is possible to measure the quality of software in terms of defects found, for both
functional and non-functional software requirements and characteristics (e.g., reliability, usability,
efficiency, maintainability and portability).
Testing can give confidence in the quality of the software if it finds few or no defects. A properly designed
test that passes reduces the overall level of risk in a system. When testing does find defects, the quality
of the software system increases when those defects are fixed.
Lessons should be learned from previous projects. By understanding the root causes of defects found in
other projects, processes can be improved, which in turn should prevent those defects from reoccurring
and, as a consequence, improve the quality of future systems. This is an aspect of quality assurance.
Testing should be integrated as one of the quality assurance activities (i.e. alongside development
standards, training and defect analysis).

Test Planning and Control


Test Planning is the activity of defining the objectives of testing and specifications of test activities in
order to meet the objectives and mission.
Test Control is the ongoing activity of comparing actual progress against the Plan, and reporting the
status, including deviations from the plan. It involves taking actions necessary to meet the mission and
objectives of the project. In order to control testing, the testing activities should be monitored throughout
the project. Test planning takes into account the feedback from monitoring and control activities.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy