4.Gray-box testing: have some knowledge of the internal structure but not in detailed to design test cases and test the application from the outside
4.Gray-box testing: have some knowledge of the internal structure but not in detailed to design test cases and test the application from the outside
## Simple techniques
## Simple techniques
- Specfication-based testing (black box):
- Specfication-based testing (black box):
1. Equivalence partitioning:You divide a set of test conditions into groups or sets that can be considered the same ( the system handle them equivalently). We need test only one condition from each partition. If one in a parttion does not work, we assume none in that partition work. You may try more than one value from a partition.
1. Equivalence partitioning:You divide a set of test conditions into groups or sets that can be considered the same ( the system handle them equivalently). We need test only one condition from each partition. If one in a parttion does not work, we assume none in that partition work. You may try more than one value from a partition.
Ex:Test the software that calculate the interest due, identify the range of balance values that earn the different rates of interest. $0-$100: 3% interest rate, $100-$1000: 5% interest rate, >=1000$: 7% interest rate.
Ex:Test the software that calculate the interest due, identify the range of balance values that earn the different rates of interest. $0-$100: 3% interest rate, $100-$1000: 5% interest rate, >=1000$: 7% interest rate.
...
@@ -31,6 +32,7 @@
...
@@ -31,6 +32,7 @@
4. Use case testing: Use cases describe the process flows through a system based on its most likely use. This makes the test cases derived from use cases particularly good for finding defects in the real-world use of the system (i.e. the defects that the users are most likely to come across when first using the system)
4. Use case testing: Use cases describe the process flows through a system based on its most likely use. This makes the test cases derived from use cases particularly good for finding defects in the real-world use of the system (i.e. the defects that the users are most likely to come across when first using the system)
- Structure-based testing(white-box):
- Structure-based testing(white-box):
1. Statement coverage and statement testing:
1. Statement coverage and statement testing:
__Statment Coverage=(Number of statements exercised/Total number of statements) X 100%__
__Statment Coverage=(Number of statements exercised/Total number of statements) X 100%__
...
@@ -93,6 +95,7 @@ coverage
...
@@ -93,6 +95,7 @@ coverage
This now covers both of the decision outcomes True and False.
This now covers both of the decision outcomes True and False.
- Experience-based testing:
- Experience-based testing:
1. Error guessing:
1. Error guessing:
Error guessing is a technique that is used as a complement to other more formal techniques. There are no rules for error guessing. The tester should think of situations in which the software may work incorrectly.Typical conditions includes division by zero, blank input, empty files and the wrong kind of data (e.g. alphabetic characters where numeric are required).
Error guessing is a technique that is used as a complement to other more formal techniques. There are no rules for error guessing. The tester should think of situations in which the software may work incorrectly.Typical conditions includes division by zero, blank input, empty files and the wrong kind of data (e.g. alphabetic characters where numeric are required).
