1- Software testing: is a way to assess the quality of the software
and to reduce the risk of software failure in operation.
2- Dynamic testing: is a testing which does involve the execution of
the component or system being tested.
3- Static testing: is a testing does involve the execution of the
component or system being tested.
4- Objectives of Testing:
To prevent defects by evaluate work products such as
requirements, user stories, design, and code
To verify whether all specified requirements have been fulfilled
To check whether the test object is complete and validate if it
works as the users and other stakeholders expect
To build confidence in the level of quality of the test object
To find defects and failures thus reduce the level of risk of
inadequate software quality
To provide sufficient information to stakeholders to allow them
to make informed decisions, especially regarding the level of
quality of the test object
To comply with contractual, legal, or regulatory requirements or
standards
5- Errors, Defects, and Failures: A person can make an error
(mistake), which can lead to the introduction of a defect (fault or
bug) in the software code or related work product. If a defect in
the code is executed, this may cause a failure
6- A/B testing: A statistical testing approach to determine which of
two systems or components performs better.
7- Acceptance criteria: The criteria that a component or system
must satisfy in order to be accepted by a user, customer, or other
authorized entity.
8- Acceptance testing: A test level that focuses on determining
whether to accept the system.
9- Accessibility: The degree to which a component or system can be
used by people with the widest range of characteristics and
capabilities to achieve a specified goal in a specified context of
use.
10- Actual result: The behavior produced when a component or
system is tested.
11- Debugging: is the development activity that finds, analyzes,
and fixes such defects
12- Defect: An imperfection or deficiency in a work product
where it does not meet its requirements or specifications.
13- Reasons that cause failures:By
1.defects in the code
2.environmental conditions. For example, radiation,
electromagnetic fields, and pollution can cause defects in
firmware
3.influence the execution of software by changing
hardware conditions
14- Error: A human action that produces an incorrect result
15- Failure: An event in which a component or system does not
perform a required function within specified limits.
16- Quality: The degree to which a component or system satisfies
the stated and implied needs of its various stakeholders.
17- False positives: occur due to errors in the way tests were
executed, or due to defects in the test data, the test
environment, or other test ware, or for other reasons. false
positives are reported as defects, but aren’t actually defects.
18- False negatives: are tests that do not detect defects that
they should have detected.
19- Quality Assurance: Activities focused on providing
confidence that quality requirements will be fulfilled.
20- Quality control: involves various activities, including test
activi1ties, that support the achievement of appropriate
levels of quality.
21- Root Cause: A source of a defect such that if it is removed,
the occurrence of the defect type is decreased or removed.
22- The root causes of defects: are the earliest actions or
conditions that contributed to creating the defects.
23- Test Analysis: The activity that identifies test conditions by
analyzing the test basis.
24- Test Basis: The body of knowledge used as the basis for
test analysis and design.
25- Test Case: A set of preconditions, inputs, actions (where
applicable), expected results and postconditions,
developed based on test conditions.
Software Testing Hand Written Notes PDF
© 2023, PDF Notes Download.com. All rights reserved.