Please enable JavaScript.
Coggle requires JavaScript to display documents.
Foundations of Software Testing (Chapter 1(Fundamentals of Testing)…
Foundations of Software Testing
Chapter 1(Fundamentals of Testing)
Section 1.1
Why testing is necessary
Example
Section 1.2
What is testing
How testing can find defects
Confirmation testing
Debuggin
Re-Testing
Requirement
Review
Test case
Test control
design specification
Testing
Test objective
Section 1.3
the fundamental principles of testing
Testing show
presence of
defect
Exhaustive
testing is
impossible
Early testing
Defect
clustering
Pesticide
paradox
Testing is
context
dependent
Absence-oferrors
fallacy
Complete Testing
Exhaustive Testing(is impossible)
Test strategy: High -level description of test level to performed
Section 1.4
the fundamental test process
Test planning and control
Test plan
Test monitoring
Test analysis and design
Test conditions
Test basis
Test data
Test corverage
Test implementation and execution
Implementation: the major tasks(page 16)
Test procedure specification
Test suite(collaps some test case): điều kiện sau thử ngiệm làm điều kiện tiên quyết cho tiếp theo
Execution: the major tasks(page 17)
Evaluating exit criteria and reporting
Test log
Test summary report
Test closure activities
major tasks( page 18)
Section 1.5
psychology of testing
The mindset between tester and developer(page 19)
Tester's mindset( page 20)
independence of testing
Test policy
Section 1.6
Code of Ethic
Time to time encounter
Chapter 2 (Testing throughout the software life cycle)
Section 2.1
V-mode
4 test levels
Component testing:searches for defects in and verifies the functioning of
software components (e.g. modules, programs, objects, classes, etc.) that are
separately testable
integration testing:tests interfaces between components, such as an operating system, file system and hardware
or interfaces between systems
system testing:concerned with the behaviour of the whole system/product. The main focus of system testing is verification against specified requirements
acceptance testing:validation testing with respect to user needs, requirements, and business processes conducted to determine whether or not to accept the system
(commercial off-theshelf software,
COTS) developed for the general market
a large number of
customers
Performance The
degree, processing
time and throughput
rate.
Rapid Application Developmen(RAD)
Agile software developmentbased on iterative incrementaldevelopment,
where requirements and solutions evolve through collaboration between self-organizing cross functional teams
Agile manifesto
individuals and interactions over processes and tools
l working software over comprehensive documentation
l customer collaboration over contract negotiation
l responding to change over following a plan.
Waterfall model(page 28)
a part is focused on validation
a part of testing is focused on Vertification
Section 2.2
Presentation - Appearance, complimentary framing and/or mounting
Chapter 3 (Static techniques)
Section 3.1
Static Testing
Testing of a component or system at specification or implementation level without execution of that software, e.g.reviews or static analysis
Advantage
Importance
Dynamic Testing
Testing that involves the execution of the software of a component or system
Concept of review
Section 3.2
Types of reviews
Informal review -
What is informal review
Formal review
What is formal review
Peer review product
by colleague
identifying defects and
improvements. Examples
are inspection, technical
review and walkthrough
Technical Review
often perform as peer review
without management participation
Walkthrough
Inspection
a type of peer review-most formal one
Phase: Planning
Moderator
Entry criteria
Kickoff
Preparation
Review meeting
Rework
Follow-up
metric
Chapter 4 (Test design techniques)
Section 4.1
Test condition
Test case
Test procedure
Teamwork.
Highest Score.
Chapter 5 (Test Management)
Leadership skill
Accomplishing tasks and activities.