Name : Date :
Test Case 2. A set of test inputs, execution conditions, and expected results
developed for a particular objective
Negative Testing 5. Type of testing that covers alphanumeric validation and blank
or zero-value entries
White-box testing 10. This uses the internal structure of the program to derive the
test cases
Sanity Testing 11. Cursory testing that covers basic functionality to demonstrate
database stability, application connectivity, etc.
Performance Test 12. Testing to verify the load, volume and response times as
defined in the requirements
Page 1
Regression Testing 13. The objective of this is to verify stability of unchanged
functionalities of the software
Test Report 15. Prepared to document test results, statistics and any deviations
from what was planned (as defined in the Test Plan).
C. Identify at least three scenarios that need to be tested to address each requirement
stated. Define any assumptions made, if necessary.
a. Generate one reminder notice for each customer who has an outstanding
balance due and who has not paid within the last 30 days.
Scenario A:
- Outstanding Balance > 0
- Minimum Amount Due Paid after the Last Payment Date = 0
- Current Date < 30 days from the Last Payment Date
Expected Result: A reminder notice will be sent to the customer
Page 2
- Outstanding Balance > 0
- Minimum Amount Due Paid after the Last Payment Date = 0
- Current Date = 30 days from the Last Payment Date
Expected Result: A reminder notice will be sent to the customer
- Outstanding Balance = 0
- Minimum Amount Due Paid after the Last Payment Date = 0
- Current Date > 30 days from the Last Payment Date
Page 3
Expected Result: No reminder notice will be sent to the customer as the customer
has no outstanding balance
b. The 30-day period is counted from the day when the customer’s last payment
was received or from the day when the customer was last sent a bill or a reminder
notice.
Scenario A Customer has the following information:
- Outstanding Balance of the borrower > 0
- Reminder Notice/Bill was sent on 11/02/2018
- Last Payment Date = 11/
- Due Date of the payment =
- Minimum Amount Due Paid by the customer
D. Indicate in the blank provided – “T”, if the requirement is completely testable, and “F”, if
the requirement is flawed. If “F”, identify what the flaw is in the particular requirement,
and list all possible questions that will help clarify the user requirements.
T a. The wording of the reminder notice must comply with all pertinent
legal and local regulations.
I marked this as completely testable as i
Page 4
Do we have any preferred indicator display on a staff whether a notice has
been sent in a timely manner?
Will there be any system generated tick marks that can be generated
together in the reminder notices?
Page 5
T e. A reminder notice is generated only if the customer has an outstanding
balance due on the day the reminder is to be generated. The
outstanding balance is the net total amount owed by the customer on
any day.
F f. If the bill was never sent to the customer and a reminder notice has been
generated, ensure that the account officer reviews and approves it
before it is sent out.
Ensuring that the account officer reviews and approves the bill is a
manual process.
Testing will include insuring that an alert or task will be created for the
account officer to review and approve if a bill was never sent to a
customer. The account officer may manually close or marked the task
or alert as completed.
Page 6
Page 7