1. Rekayasa Perangkat Lunak Part-13
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

2. Outline of this presentation
Who Tests Software
Testing Technique
Testing Step
Testing Strategy
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

3. Who Tests Software? user independent tester developer
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

4. Who Tests Software? Software Developer Independent Tester
Understand system
Test gently
Driven by delivery
Independent Tester
Doesn’t understand system
Will try to break it
Quality driven
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

5. Who Tests Software? User Test while using it Indirect test
It’s not in purpose to do so
Indirect test
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

6. Static verification Review (desk checking)
Code reading done by a single person,
informal.
Uneffective compared to walkthrough or inspection
Walkthrough
The programmer(s) ”walks through”/”executes” his code while invited participants ask questions and makes comments.
Relatively informal
Inspection
Usually a checklist of common errors is used to compare the code against.
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

7. Testing Technique White Box Testing Black Box Testing
Two views on Software testing:
White Box Testing
Black box
Black Box Testing
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

8. Testing Technique White box testing - tests what the program does.
Test sets are developed by using knowledge of the algorithms, data structures, and control statements.
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

9. Testing Technique
Black box testing - tests what the program is supposed to do.
Test sets are developed and evaluated solely on the specification. There is no knowledge of the algorithms, data structures, or control statements.
Black box
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

10. White-box testing Also known as: Structure based (Structural) testing
Code based testing
Glass box testing
Clear box testing
Logic driven testing
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

11. White-Box Testing White-box (or Structural) testing:
Use knowledge of the program to derive test cases to provide more complete coverage
Problem: What criteria to use?
Two basic strategies for figuring out a test plan: black-box or white-box. (There are also points inbetween.) One is not better than the other. Black-box testing uses boundary analysis, input equivalence partitioning, etc.
We’ll be focusing on white-box. We’ll go through a quick example on the board about the differences.
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

12. White-Box Testing ... our goal is to ensure that all
Statements, decisions, conditions, and paths have
been executed at least once ...
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

13. White-box testing The system is looked upon as an open box.
The test cases is based on the internal structure of the system (code)
Theoretically desirable but impossible and insufficient goal: all paths of the code exercise
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

14. Black-box testing Also known as: Functional Testing
because it test all the functions
Behavioral Testing
because the program is tested against the expected behavior (described by requirements and/or design)
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

15. Black-box testing requirements output input events
The software is viewed as a black box which transforms input to output based on the specifications of what the software is supposed to do.
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

16. Black-box testing
Check The Conformity of the tested S/W against established behaviour, and
Detect errors generated by fault
Software fault is a software part which is not according to its definition provided in the development document
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

17. Black-box testing
Functional tests examine the observable behavior of software as evidenced by its outputs without reference to internal functions.
If the program consistently provides the desired features with acceptable performance, then specific source code features are irrelevant.
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

18. Black-box testing Should consider only from the standpoint of its:
Input data
Output data
Knowledge of its internal structured should not be
It is very often impossible to test all the input data
It is hence necessary to select a subset of possible input
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

19. Testing Steps Unit Unit code test . SYSTEM IN USE! Integration
Function
Performance
Acceptance
Installation
Unit code .
Integrated
modules
Functioning
system
Verified,
validated
software
Accepted
SYSTEM
IN USE!
Design
specifications
System
functional
requirements
Other
Customer
specification
User
environment
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

20. Testing Steps Acceptance Test
software
tests
customer
developer site
type of acceptance testing performed by customer at the developer’s site is usually called alpha testing
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

21. Testing Steps Acceptance Test
software
customer site
customer
tests
beta testing is a type of acceptance testing involving a software product to be marketed for use by many users
selected users receive the system first and report problems back to the developer
users enjoy it - usually receive large discounts and feel important
developers like it - exposes their product to real use and often reveals unanticipated errors
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

22. Testing Strategy Big Bang! Top-down Sandwich Bottom-up incremental
non-incremental
incremental
Sandwich
Compromise
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

23. Testing Strategy Big bang integration (all components together)
Bottom up integration
(from lower levels No test stubs necessary)
Top down integration
(from higher levels  no test drivers are needed)
Sandwich testing
(combination of bottom-up and top-down  no
test stubs and drivers needed)
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi

24. Finished,
Questions?
Rekayasa Perangkat Lunak Copyright © Feb-2009 by Fakultas Teknologi Informasi