This document provides an overview of software testing concepts and processes. It discusses why testing is important, defines common testing terms, and outlines the typical phases of a testing lifecycle including planning, analysis, implementation, evaluation, and closure. It also describes different testing techniques like static reviews, functional testing, and performance testing. Risks of poor quality like defects, failures, and their impacts on humans, economy, business are highlighted. The roles of testers and differences between quality assurance and quality control are defined. Examples of testing in various industries are provided.

1. Prepared by:
Asmaa F. Matar.
Mona M. Abd El-Rahman.

2.  Why testing is necessary ?
 What is testing ?
 Testing principals.
 Testing process.
 Why testers ?
 Testing in development life cycle.
 Configuration management.
 QC vs QA.

4. .
 Health equipment.
 Transportations.
 Banking
 Insurance
 Education
 Scientific Research

5. Risks
(Poor Quality)
Humans
(Death, Injury)
Economy
(Money, Time)
Business
(Revenue,
Reputation)

6.  Msnbc published the news of 2010 bug hits
millions of German bank cards.
Guardin.co.uk said they paid about (€300m).
 Apple Maps gives us directions to nowhere
(2012).

7.  Find defects.
 Measure quality.
 Provide confidence.

8. Errors
&
Mistakes
- Documents.
- Code
- Software system
Defect or Fault
Failure

9. Defect
Injection
Detection
Prevention
- A defect injected at the time
the causing error is made.
- A defect is detected at
The time when failure occurs.
- Finding defects in
requirements docs or static
code can prevent detecting
them in running systems.

11. “The process consisting of all life cycle
activities, both static and dynamic concerned
with planning , preparation and evaluation of
software products and related work products to
determine that they satisfy specified
requirements , to demonstrate that they are fit for
purpose and to detect defects”.
It can be defined as:

13. Suppose You are given “Pen” with instructions to
test it .
What will you do ?

14. Testing
Static
Reviews
Dynamic
Functional
Non-
Functional
Performance Security Usability

15.  Testing Shows Presence of defects.
 Exhaustive testing is impossible.
 Early Testing.
 Defect Clustering.
 Pesticide Paradox .
 Testing is context dependent.
 Absence of errors fallacy.

17. Planning
and
Control
Analysis
and
design
Implemen
tation and
execution
Evaluating
Exit criteria
And
reporting
Closure

18.  Ongoing comparison of actual progress
against plan.
 Reporting status.
 Takes into account feedback of monitoring and
control.

19.  Reviewing the test basis.
 Evaluating testability of test basis and test
objects.
 Identifying and prioritizing test conditions
 Designing and prioritizing test cases.
 Identifying necessary test data
 Designing the test environment set-up and
identifying any required infrastructure and tools.

20.  Creating test cases , writing test procedures.
 Creating test suits.
 Prepare test execution plans.

21.  Execute test cases.
 Logging test outcomes and related details.
 Checking results and reporting.
 Running confirmation and regression testing.

22.  Checking test logs against the exit criteria
specified in the planning.
 Assessing if more tests are needed.
 Writing a test summary report for stake
holders.

23.  Checking that deliverables have been
delivered as planned.
 Archiving the test environment and the test
infrastructure for later reuse.
 Analyzing lessons learned for future releases
and projects .

25. The amount of testing needed is proportionate
with:
 Risk.
 Defect cost.
 Information needed.
 Project constraints.
 Test infrastructure.

27. Breakdown
Build

28.  Curiosity.
 Clear thinking skills.
 Top flight reading speed and comprehension.
 Attention to details.
 Quick learner (outside of testing).

29. Component Test
Integration test
System test
Acceptance
Test

31. Waterfall
(Sequential development model)
Requirements
Analysis
Design
Code
Test

32. Requirements
Analysis
Design
Code Component test
Integration test
System test
Acceptance test
V-Model

33. W-Model

34. Iterative incremental

36. The purpose of configuration management is to
establish and maintain the integrity of the
products (components, data and documentation)
of the software system through the project and
product lifecycle.

37. Configuration Management will ensure the
follow:
- All items of testware are
identified, version
controlled, tracked for
changes related to each
others and related to
development items (test
objects) so that
traceability can be
maintained throughout the
test process.
- All identified documents
and software items are
referenced unambiguously
in the test documentation for
the tester, configuration
management helps to
uniquely identify and
reproduce the test item, test
documents, the tests and test
harness.

38. Benefits
To
Testing
Traceability
Clear
Documentation
Unique
Identification

39. How to report an incidents ?!
 Incident Id.
 Clear title.
 Link to a test case and a user story.
 Tester name.
 Detected in: Build No.
 Solved in: Build No.

40.  Assigned to:
 Test environment.
 Scenario to reproduce the bug.
 Actual results.
 Attach screenshots or videos.
 Expected Results.

42. Quality Assurance (QA) Quality Control (QC)
Definition
Set of activities for ensuring
quality in the processes by which
products are developed.
Set of activities for ensuring
quality in products. The
activities focus on identifying
defects in the actual products
produced
Aims to
Prevent defects with a focus on
the process used to make the
product. It is a proactive quality
process.
Identify (and correct) defects
in the finished product.
Quality control, therefore, is a
reactive process
Goal
Improve development and test
processes so that defects do
not arise when the product is
being developed.
Identify defects after a
product is developed and
before it's released.

44. Feel free to contact us
Asmaa.matar@it-qan.com
Mona.m.abdelrahman@gmail.com