The document outlines fundamental principles of testing, including static and dynamic testing techniques, emphasizing the importance of examining product specifications to uncover bugs early in the development process. It discusses methods for high-level reviews, the need to understand customer expectations, and research on existing standards and guidelines. Additionally, it highlights key attributes of effective specifications and provides checklists for terminology and low-level testing methods.

1. Swati Jitendrakumar Patel
Testing FundamentalsTesting Fundamentals

2. Contents
Examining the specification
Getting Started
Black-box and White-box Testing
Static and Dynamic Testing
Static Black-box Testing: Testing the Specification
Performing High-Level Review of the Specification
Pretend to be the Customer
Research Existing Standards and Guidelines
Review and Test Similar Software
Low-Level Specification Test Techniques
Specification Attributes Checklist
Specification Terminology Checklist

3. ExaminingExamining thethe specificationspecification
 The product Specification is examined to discover bugs
before the affect the software
 Finding bugs at this stage can potentially save your
project huge amounts of time and money

4. Getting Started

5. Black-box and White-box Testing
Getting Started Cont..

6. Static Testing:
Examining and reviewing something that is not running
Ex: 1. kicking the tires
2. Checking the paint
3. Looking under the hood
Dynamic Testing:
Examining and reviewing something that is in running state
Ex: 1. Starting it up
2. Listening to the engine
3. Driving down the road
Getting Started Cont..
Static and Dynamic Testing

7. Static Testing:
Examining and reviewing something that is not running
Ex: 1. kicking the tires
2. Checking the paint
3. Looking under the hood
Dynamic Testing:
Examining and reviewing something that is in running state
Ex: 1. Starting it up
2. Listening to the engine
3. Driving down the road
Getting Started Cont..
Static Black-Box Testing: Testing the Specification

8. Pretend to be the Customer
 To think who the customers would be
 Know about the end user from marketing or sales
people
 If product is an internal software project then find out
who will be using it
To communicate with end users about their expectations
To generate a QUALITY product.
Performing High-Level Review of the Specification
Research Existing Standards and Guidelines

9. Research Existing Standards & Guidelines
Performing High-Level Review of the Specification cont.
Research Existing Standards and Guidelines
 Corporate terminology and
conventions
 Industry Requirements
 Government Standards
 Graphical User Interface (GUI)
 Security Standards

10. Review and Test Similar Software
Performing High-Level Review of the Specification cont.
Research Existing Standards and Guidelines
Some things to look for when reviewing
competitive products include
 Scale
 Complexity
 Testability
 Quality/Reliability
 Security

11. Specification Attributes Checklist
Low-Level Specification Test Techniques
Research Existing Standards and Guidelines
Product specification has 8 important attributes:
 Complete
 Accurate
 Precise, Unambiguous and Clear
 Consistent
 Relevant
 Feasible
 Code-free
 Testable

12. Specification Terminology Checklist
 Always, Every, All, None, Never
 Certainly, Therefore, Clearly, Obviously, Evidently
 Some, Sometimes, Often, Usually, Ordinarily,
Customarily, Most, Mostly
 Etc., And So Forth, And So On, Such As
 Good, Fast, Cheap, Efficient, Small, Stable
 Handled, Processed, Rejected, Skipped, Eliminated
 If…Then…(but missing Else)
Low-Level Specification Test Techniques cont.

13. Reference
“Software Testing”
by
Ron Patton