Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
9 views10 pages

Test Principles

The document outlines key principles of software testing, emphasizing that testing aims to identify defects and improve quality. It highlights that exhaustive testing is impossible, and testing should be context-dependent and risk-driven, focusing on high-risk areas. Additionally, it stresses that testing is a continuous process and that complete testing is unattainable, necessitating prioritization of testing efforts.

Uploaded by

kimxx894
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
9 views10 pages

Test Principles

The document outlines key principles of software testing, emphasizing that testing aims to identify defects and improve quality. It highlights that exhaustive testing is impossible, and testing should be context-dependent and risk-driven, focusing on high-risk areas. Additionally, it stresses that testing is a continuous process and that complete testing is unattainable, necessitating prioritization of testing efforts.

Uploaded by

kimxx894
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

Test Principles

Test Principles
• Testing principles are fundamental guidelines and concepts that help
ensure the effectiveness and efficiency of the software testing
process.
• These principles guide testing activities, methodologies, and
strategies to identify defects and improve the overall quality of
software.
Testing Shows the Presence of Defects
• Testing is primarily aimed at finding defects in software.
• The goal is to identify and address issues to improve software quality.
Exhaustive Testing is Impossible
• Testing should start as early as possible in the software development
life cycle.
• This helps identify and fix defects at the earliest stages, reducing the
cost and effort of fixing issues later in the development process.
Defect Clustering
• A small number of modules or functionalities in software typically
contain the majority of defects.
• Test efforts should be concentrated on these high-risk areas to
maximize the effectiveness of testing.
Testing is Context-Dependent:
• The approach to testing should be tailored to the specific context of
the project.
• The nature of the software, the project's goals, and the available
resources all influence the testing strategy.
Absence-of-Errors Myth
• Finding and fixing defects does not guarantee that a system is defect-
free.
• It is important to consider other aspects of quality, such as usability,
performance, and security.
Risk-Driven
• Testing efforts should be prioritized based on the risks associated with
the software.
• Focus on testing areas that have a higher likelihood of defects or that
could have a significant impact on the system or users.
Testing is a Continuous Process
• Testing is not a one-time activity but a continuous process that occurs
throughout the software development life cycle.
• As the code evolves, testing activities need to be adapted and
extended accordingly.
Complete Testing is Impossible
• Complete testing of software under all possible conditions is
practically impossible.
• Testing efforts should be based on priorities and should cover the
most critical and probable scenarios.

You might also like