This document provides an overview of software testing fundamentals. It discusses why testing is necessary due to human errors that can lead to defects. It then defines software testing as a process used to evaluate a product against requirements and design specifications through execution of tests to detect defects. The document outlines the general test process, including test planning, analysis and design, implementation and execution, evaluating results against exit criteria, and closing testing activities.

1. FUNDAMENTAL OF TESTING
AHMED AL ZAIDY

2. FUNDAMENTAL OF TESTING
• Why is testing necessary?
• What is testing?
• General testing principles
• Fundamental test process
• The psychology of testing
• Code of ethics
Test Planning and Control
Test Analysis and Design
Test Implementation and
execution
Evaluating exit criteria and
reporting
Test Closure activities

3. WHY IS TESTING
NECESSARY?
• Human make mistakes
• Mistakes – unimportant,
expensive or dangerous
• Must check – some things can
always go wrong
• Mistakes may comes from:
• Bad assumption
• Blind spot

4. SOFTWARE SYSTEMS CONTEXT
• Software that did not work as expected?
• Error on a bill, delay on credit card processing, website that did not load correctly etc.
• Different software carry different level of risk
• Problems – trivial, costly and damaging (loss of money, time or business reputation, or results in injury
or death
RISK: A factor that could result in future negative
consequences; usually expressed as impact and likelihood

5. CAUSES OF SOFTWARE DEFECTS
• People who design or build the software can make mistakes
• Mistakes means flaws in the software => defects/bugs/faults
• Defects may caused system to fail to do what it should do (or do something
it shouldn’t) => causing failure
Error
(Mistakes)
Defects
(Bugs/Faults)
Failure

6. DO OUR MISTAKES MATTER?
• Think about the consequences of mistakes…
• Human being, programmer, tester => can make error
• Error => defects => defect code executed => systems failure
• Systems and project are complicated

7. DEFECTS & FAILURES
• Errors in specifications, design and implementation
• Errors in use of the systems
• Environmental conditions
• Intentional damage
• Potential consequences of earlier errors, intentional damage, defects and failures

8. WHEN DO DEFECTS ARISE?
Requirement 1
Correct requirement
Designed to meet
requirement
Build to meet design
Product works as
expected
Requirement 2
Correct requirement
Designed to meet
requirement
Mistakes
made in build
Product
has bugs in it

9. WHEN DO DEFECTS ARISE?
Requirement 3
Correct requirement
Mistake made in
design
Built to meet
design
Product has design
flaws
Requirement 4
Mistakes made in
requirement
Design to meet requirement
Built to meet design
Wrong product delivered

10. WHAT IS COST OF DEFECTS?
• The cost of finding and fixing the defects rises considerably across the life
cycle
Cost
Time
Requirements Design Build Test Live use

11. ROLE OF TESTING IN SOFTWARE DEVELOPMENT,
MAINTENANCE & OPERATIONS
• We have seen human errors can caused defect or fault at any stage of software development life-cycle
• Rigorous testing is necessary during the maintenance & development to identify defects => to reduce
failures in operational environment
• To increase quality of operational systems
• Executing tests helps us move towards improved quality of product and services

12. TESTING & QUALITY
• Testing helps us to measure quality of software in terms of:
• The number of defects found
• The number of tests run
• The system covered by the test
• Both functional and non-functional software requirements
• Testing gives us confidence in quality
• Poor test may uncover few defects

13. WHAT IS QUALITY?
• Project aim to deliver software that meet customer needs & correct specification
• Validation – “ is this the right specification”
• Verification – “is the system correct to specification”
• Need to understand what customer understand by quality and what their expectation are

14. WHAT IS ROOT CAUSE ANALYSIS?
• Detect failures => track them back to their root cause
• Several ways & involving a group brainstorming ideas and discussion
• Assignment #1:
• Find 3 ways to do Root Cause Analysis.
• Discuss how it works.

15. HOW MUCH TESTING IS ENOUGH?
• We have a choice:
• Test everything?
• Test nothing?
• Test some part?
• Example: One-digit field – how many test is enough?
• Real example: one screen with 15 input fields
• Pressures on project: time & budget
• Need test approach which provides the right amount of testing
• Risk assessment – helps to decide how much testing to do

16. WHAT IS TESTING?
• Recall the common objectives of testing
• What is testing? – checking if the software is OK?
• Lets discuss an analogy of: driving test
• The format of the driving test and conduct of examiner:
• The test is planned & prepared
• The test has known goals
• The test is therefore carried out to show that the driver satisfied the requirement for driving & demonstrate
that they are fit to drive

17. DEFINING SOFTWARE TESTING
• ISTQB definition of software testing
• Process – Testing is a process rather a single activity – there are series of activities
• All life cycle activities – software development life cycle (discuss this in Chapter 2)
• Requirements
• Design (to prevent defects introduced into code) – test via the test design

18. DEFINING SOFTWARE TESTING
• Both static and dynamic
• Dynamic testing – execute codes & demonstrate the results
• Static – reviewing documents including the source code
• Planning – to manage the testing: plan, control, report testing progress, close testing
• Preparation – selecting test conditions & design test cases
• Evaluation – check results and evaluate software under test & completion criteria
• Software products and related work product – not only test code, requirements & design specification

19. DEFINING SOFTWARE TESTING
• Objectives for testing
• Determine the software product satisfy specified requirements
• Demonstrate that the software products are fit for purpose
• Detect defects
• Objectives may be different in each stage

20. GENERAL TESTING PRINCIPLES
• Principle 1: Testing shows the presence of defects
• Principle 2: Exhaustive testing is impossible
• Principle 3: Early testing
• Principle 4: Defect clustering
• Principle 5: Pesticide paradox
• Principle 6: Testing is context dependent
• Principle 7: Absence-of-errors fallacy

21. FUNDAMENTAL TEST PROCESS
• Fundamental test process:
• Planning and control
• Analysis and design
• Implementation and execution
• Evaluation exit criteria and reporting
• Test closure activities

22. TEST PLANNING AND CONTROL
• We make sure we understand the goal and objectives of the customer, stakeholders, the project and the
risks
• Based on the understanding, we set the goal & objectives for the testing itself
• To help us, we may have:
• Test policies – rules for testing
• Test strategy – Overall high-level approach

23. TEST PLANNING AND CONTROL
• Test planning has the following major task:
• Determine the scope and risks; Identify the objectives of testing
• Determine the test approach (techniques, test items, coverage, identifying and
interfacing the teams involve in testing, testware)
• Implement the test policy and/or the test strategy
• Determine the required test resources (people, test environment, PCs)
• Schedule test analysis and design tasks, test implementation, execution and
evaluation
• Determine the exit criteria

24. TEST PLANNING AND CONTROL
• Test control is an on-going activity
• We compare the actual progress with planned progress
• Test control has the following major tasks:
• Measure & analyze the results of reviews and testing
• Monitor and document progress
• Provide information on testing
• Initiate corrective actions
• Make decisions

25. TEST ANALYSIS AND DESIGN
• Test analysis and design has the following major tasks:
• Review the test basis (product risk analysis, requirements, architecture, design specification and interface)
• Identify test conditions (behavior and structure)
• Design the test (Chapter 4)
• Evaluate testability of the requirements and systems
• Design the test environment set-up and identify any required infrastructure and tools

26. TEST IMPLEMENTATION AND EXECUTION
• Implementation:
• We take the test conditions and make them into test cases and set up the test environment
• Having the high-level design – we now build them
• We set up the environment
• Build our test data
• Execution:
• Execute the test cases
• Log the outcome of test execution
• Compare actual result with expected result

27. EVALUATING EXIT CRITERIA AND REPORTING
• Is an activity where test execution is assessed against the defined objectives
• Evaluating exit criteria involve following major tasks:
• Check the test logs against the exit criteria
• Assess if more test needed
• Write a test summary report

28. THANK YOU!
SOMEONE@EXAMPLE.COM