Beruflich Dokumente
Kultur Dokumente
Equivalence Class
Valid
a-z
09
Invalid
A-Z
Special
Blank
Equivalence Class
Invalid
a
0-9
Special Chars
Blank
User
Password
Valid Value
Valid Value
Invalid Value
Blank Value
Valid Value
Invalid Value
Blank Value
Blank Value
Criteria
Valid Value
Invalid Value
Valid Value
Valid Value
Blank Value
Blank Value
Invalid Value
Blank Value
Pass
Fail
Fail
Fail
Fail
Fail
Fail
Fail
Functional specification 2:
In an insurance application, can apply for different
types of policies.
From customer requirements, the system asks age, when a user
selects type insurance. The age value should be >17 years and should
be <60 years.
Prepare test case titles:
Test case title 1: Verify type A insurance selection.
Test case title2: verify age focus when selects type A insurance.
Test case title3: verify age value
Boundary valueAnalysis (BVA)
partition (Type)
Equallyclass
Valid
Invalid
0-
A-Z
Special Characters
Blank
Equivalence
Invalid
09
a-z
A-Z
Special Characters
Blank
Test case title 3: verify total = price of one item X given quantity.
Suppose the specifications for a database product state that the product must be able to
handle any number of records from 1 through to 16,383. If the product can handle 34
records and 14,870 records, then the chances are good that it will work fine for, say,
8534 records. If the product works correctly for any one test case in the range 1 to
16,383, then it will probably work for any other test case in the range. The range from 1
to 16,383 constitutes an equivalence class. For this product, there are three
equivalence classes:
Testing the database product then requires that one test class from each equivalence
class be selected.
A successful test case is one that detects a previously undetected fault. In order to
maximise the chances of finding a new fault, a high-payoff technique isboundary-value
analysis. Experience has shown that when a test case on or just to one side of a
boundary of an equivalence class is selected, the probability of detecting a fault
increases. Thus, when testing the database product, the following cases should be
selected:
Test case 1:
0 records
Test case 2
1 record
Boundary value
Test case 3
2 records
Test case 4
723 records
Test case 5
16,382 records
Test case 6
16,383 records
Boundary value
Test case 7
16,384 records