Fundamentals

of Software
Testing
What is software?

- COLLECTION OF INSTRUCTION THAT ENABLE THE USER TO INTERACT

WITH
 THE COMPUTER-HARDWARE IN ORDER TO PERFORM TASK
 - SET OF PROGRAMS
 - LINE ON CODES, WHAT ABOUT LINE OF PSEUDOCODE?
 - APPLICATION/SYSTEM
What is software testing?

-THE PROCESS (ALL LIFECYCLE) OF STATIC AND DYNAMIC CONCERNED

WITH
 PLANNING, PREPARATION AND EVALUATION OF SOFTWARE
PRODUCTS
-TO DETECT THE PRESENCE OF DEFECTS
-TOACHIEVE CONFIDENCE (V&V) LEVEL FOR A PARTICULAR
SOFTWARE
-TO SHOWS THAT SOFTWARE ARE FIT FOR PURPOSE
 Software Quality

-A set of attribute of a -Quality software attributes Functional requirements Non-functional

software product by which much related to Functional requirements
its quality is described and Requirement (FR) specific
evaluated behaviors/functions and
Non-Functional
Requirement (NFR) –
Statements of services the system Constraints on the services or
should provide, how the system functions offered by the system
should react to particular inputs such as timing constraints,
and how the system should constraints on the development
behave in particular situations. process, standards, etc.
May state what the system should
not do.
 What is these? Is it a body? A company?

ISO- International Standard Organization

IEC-International Electrotechnical Commission

Software -Effectiveness : The software is able to display the output as required and
affecting
Quality- the outcome of a particular business process

ISO/IEC 9126 -Productivity: The software is able to function in required amount of

(1/2)
time/number
of functionalities

-Security : The software is able to protect data from the unauthorized

party
-Satisfaction: The software has meet the requirement of the end user
 -Functionality: The software is able to execute their features

-Reliability: The software is able to produce correct output

Software -Usability: The end user is able to perform require task using the
software without any difficulties in using the software instruments
Quality- -Efficiency : The software is able to consumed suffice memory
space of the storage
ISO/IEC 9126 devices
(2/2)-we stop -Maintainability: The software is able to be modified or fix, as well
here at w2 as operated as
required.

-Portability: The software is able to be executed on other

platform
 WEEK 2 – OBJECTIVES OF TESTING

To EVALUTE To VERIFY To VALIDATE To BUILD To PREVENT To FIND To PROVIDE To REDUCE To COMPLY To VERIFY with
work whether all whether the CONFIDEN defect such failures and sufficient the level of with test object’s
products specified test object is as when early defects – information to risk of contractual, compliance
CE in the
such as requirements complete activities. PRIME FOCUS stakeholder inadequate legal or with such
level of
requirements, has been and works as for software to allow them software regulatory requirement
quality of the
user stories, fulfilled, for the users and testing to make quality. requirement or standard.
test object
design and example in other informed or standard
such as when
code by resulting stakeholder decisions
those test
using static system. expect- for especially
considered
testing example, regarding the
highest risk
technique together with level of
pass, and
such as user or quality of the
when the
reviews. stakeholder test object.
failures that
groups. are observed
in the other
tests are
considered
acceptable.
Testing Principles

Rules in Software Policy in Software

Testing Testing

Law in Software Has been established

Testing for previous 40 years
Testing Principles)

Testing can show that defects are present, but cannot prove
Principle 1: Testing that there are no defects. Testing reduces the probability of
undiscovered defects remaining in the software but, even if no
shows presence of defects are found, it is not a proof of correctness.
defects
Testing Principles

1 2 3 4
Principle 2: Testing everything except for trivial exhaustive
Exhaustive testing (all combinations cases (There is testing, we use
is impossible of is inputs and measurement of risks and priorities
preconditions) is testing applied). to determine the
not feasible Instead of testing efforts.
Testing Principles

Testing activities should start as early as

possible in the software or system
Principle 3: Early testing development life cycle and should be
focused on defined objectives.
Testing Principles

A SMALL NUMBER OF MODULES CONTAIN MOST OF THE

PRINCIPLE 4: DEFECT DEFECTS DISCOVERED DURING PRERELEASE TESTING OR
CLUSTERING SHOW THE MOST OPERATIONAL FAILURES. GROUPING OF
DEFECTS IS VERY IMPORTANT.
Testing Principles (stop here at w1-2nd session
5g1-5h1)

IF THE SAME TESTS ARE REPEATED OVER AND OVER AGAIN, EVENTUALLY THE
SAME SET OF TEST CASES WILL NO LONGER FIND ANY NEW BUGS. TO OVERCOME
PRINCIPLE 5: PESTICIDE PARADOX THIS 'PESTICIDE PARADOX', THE TEST CASES NEED TO BE REGULARLY REVIEWED
(REPETITIONS HAVE NO EFFECT) AND REVISED, AND NEW AND DIFFERENT TESTS NEED TO BE WRITTEN TO EXERCISE
DIFFERENT PARTS OF THE SOFTWARE OR SYSTEM TO POTENTIALLY FIND MORE
DEFECTS
Testing Principles

Principle 6: Testing is Testing is done differently in different contexts.

For example, safety-critical software is tested
context dependent differently from an e-commerce site.
Testing Principles

Principle 7: Absence-of-errors fallacy

Finding and fixing defects does not help if the system built is
unusable and does not fulfill the users' needs and expectations
(not necessary to pass validation test/fail the validation test).
References

FOUNDATIONS OF SOFTWARE TESTING ISTQB CERTIFICATION, Dorothy Graham, Erik van Veenendaal, Isabel Evans, Rex Black

http://www.istqb.org/downloads/syllabi/foundation-level-syllabus.html

http://www.thomsonlearning.co.uk/ISTQB

http://istqbexamcertification.com/what-is-software-testing/

https://www.iec.ch/index.htm

https://www.iso.org/home.html

MSTB, 2013, Software Testing Foundations, Certified Tester page 44